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
  527D RCD03-01
  527D G6201 07 Effective Date Use to indicate when an item or transaction is prepared, becomes effective, or is placed into service Use to identify the map effective date. Use with due-in and PMR for mapping products. Authorized DLMS migration enhancement. See DLMS introductory note 4g. 8/8
  527D G6201 17 Estimated Delivery Date Use for Materiel Obligation Validation (MOV) and excessive quantity verification inquiries to identify the estimated shipping date (ESD) Must use in each due-in and PMR transaction. Use with delinquent due-in advice and due-in reconciliation advice transactions only when providing a revised date. Use with due-in reconciliation inquiry when available. 8/8
  527D G6201 52 Ordered Used to indicate an order date Commercial Asset Visibility (CAV) uses to indicate an order date in the PMR transaction. 8/8
  527D G6201 BB Transaction Control Date Use to cite the date the transaction was prepared Use to cite the date the transaction was prepared. 8/8
  527D G6201 BC Publication Date Use only when requisitioning nonstandard material to cite the manufacturer's catalog publication date when a catalog is identified Use to identify the map edition date. Use with due-in and PMR for mapping products. Authorized DLMS migration enhancement. See DLMS introductory note 4g. 8/8
  527D G6201 TR Transfer Use to identify the estimated shipping date for delayed replenishment shipments to NIMS sites for the required quantity not available for immediate shipment 1. Used to identify the estimated shipping date for delayed replenishment shipments to NIMS sites for the required quantity not available for immediate shipment. Only for use with PMR transactions (1/BR02/020 code ‘DE), with BR06 code ‘RS’ and 2/LIN02/010 code ‘N’ (relocations). An ANSI data maintenance action has been taken to establish a more appropriate qualifier. 2. DLMS enhancement. See introductory DLMS note 4a.
  527D G6202
  527D G6203 W Effective Time Use to establish unique date/time stamp Use in conjunction with G6201 code BB only to establish unique date/time stamp. Express time in six-position format (HHMMSS). This is an authorized DLMS enhancement; see introductory DLMS 5g. 4/8
  527D G6204
  527D GF01 W3 Manufacturing Directive Number The DLA source from which a commercial contractor is authorized to requisition material from DoD inventory DLMS enhancement; see introductory DLMS note 4a. 3/3
  527D GF02
  527D GF03
  527D GF07
  527D DD01
  527D DD02 MPP Mapping Product Procurement Types Use to Identify the type of procurement for mapping DD01 code values authorized for use with MPP are identified in DLM 4000.25, DLMS, Volume 2. Required for due-in and PMR for mapping products. 1/1
  527D DD03 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. Use to identify the applicable weapon system designator code. 2. DLMS enhancement; see introductory DLMS note 4a. 3/3
  527D DD04
  527D DD05
  527D DD06 71 Service and Agency Code Use to identify the Service or Agency that initiates or receives documentation related to supply, finance, procurement, etc. Use to identify the Service associated with the weapon system designator code for the due-in quantity. 1/2
  527D DD07
  527D DD08
  527D DD09
  527D DD10 MPT Mapping Product Types Use to Identify the type of mapping product 1. Use to identify Mapping Product Type. Code values authorized for DD09 entry with MPT are identified in DLM 4000.25, DLMS, Volume 2. Required for due-in and PMR for mapping products. 2. Approved for use in version 8010. 1/1
  527D N901 16 Military Interdepartmental Purchase Request (MIPR) Number Use to establish the availability of funds and to procure, perform services, or furnish material to or for the required service 1. Use for prepositioned materiel receipt (PMR) transactions to identify the Military Interdepartmental Purchase Request (MIPR) number when tracking in-process maintenance; otherwise, do not use. 2. DLMS enhancement; see introductory DLMS note 4a. 1/20
  527D N901 43 Supporting Document Number Use to identify, track, and reference a document or transaction across various processes, including procurement, receipts, and maintenance 1. Use in procurement source PMR when a document number is needed in addition to the contract number. Identify the controlling contract number in the 2/CS/020 segment. 2. Authorized DLMS enhancement for commercial repair returns shipped on a Reparable Receiving Report with a MILSTRIP document number. DLMS enhancement; see introductory DLMS note 4.b. Refer to ADC 1268. 1/30
  527D 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 PMR transactions to identify the Sort Sequence Number. 2. DLMS Component-unique enhancement. See introductory DLMS 4e. 1/30
  527D N901 6E Map Reference Use to identify the National Geospatial-Intelligence Agency (NGA) Reference Number (NRN) Use to identify the National Geospatial-Intelligence Agency (NGA) Reference Number (NRN). Use with due-in and PMR for mapping products. Authorized DLMS migration enhancement. See DLMS introductory note 4g. 1/1
  527D N901 6G Map Number Use to identify the map edition number Use to identify the map edition number. Use with due-in and PMR for mapping products. Authorized DLMS migration enhancement. See DLMS introductory note 4g. 3/3
  527D N901 74 Work Breakdown Structure (WBS) A visual, hierarchical and deliverable-oriented deconstruction of a project Use in PMR transactions. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 1128. 1/30
  527D N901 86 Operation Number Use to identify the Key Operation (KO) Number associated with the JO 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/50
  527D N901 98 Container/Packaging Specification Number Use to identify the Disposition Services Container Identification (ID) which is a unique number that is generated at time of receipt that links multiple Disposal turn-in document (DTID) to one conta8iner Use to identify the Disposition Services Container Identification (ID). DLA Disposition Services uses Disposition Services Container ID with PMR (Relocation) transactions (LIN01 code N). Authorized DLMS enhancement. Refer to ADC 410. 10/10
  527D N901 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
  527D N901 AH Agreement Number Use to identify the Depot Maintenance Inter-Service Support Agreement (DMISA) number when tracking in-process maintenance or materiel 1. Use in PMR transactions to identify the Depot Maintenance Inter-Service Support Agreement (DMISA) number when tracking in-process maintenance; otherwise, do not use. 2. DLMS enhancement; see introductory DLMS note 4a. 1/30
  527D N901 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
  527D N901 CR Customer Reference Number A unique code assigned to a customer by a company, used to identify a specific transaction or interaction, allowing for easier tracking and reference 1. Use the Customer Reference Number to cross-reference to the requisition number under which the materiel was ordered, when it differs from the turn-in/return document number used with Code TN. This is applicable to directed return of discrepant/deficient materiel and other types of retrograde shipments. 2. DLMS enhancement. Refer to ADC 353A and ADC 1249. 1/30
  527D N901 CT Contract Number A standard unique identification of a DoD procurement contract (contract number) that specifically differentiates one contract from all other contracts Use with non-procurement source transactions when a contract number is needed in addition to the transaction number for transaction tracking purposes. Identify the controlling transaction number in 2/N9/030. 1/13
  527D N901 D9 Claim Number Use to identify a Transportation Discrepancy Report (TDR) control number that is a combination of the reporting activity's Department of Defense Activity Address Code (DoDAAC), the last two digits of the year the report was created, and a four-digit sequential number when directing the return 1. Use to identify the TDR control number directing the return. Recommended for inclusion in the PMR where an automated interface with the discrepancy reporting application is available. 2. DLMS enhancement. Refer to ADC 353. 14/14
  527D N901 NN Nonconformance Report Number Use to identify Report Control Number (RCN) 1. Use to identify the DoD WebSDR control number associated with the SDR Reply directing the return. Recommended for inclusion in the PMR where an automated interface with the discrepancy reporting application is available. 2. DLMS enhancement. Refer to ADC 353. 12/12
  527D N901 Q9 Repair Order Number Identifies originating repair order number or repair document number under which repair action is being taken Identifies the Associated Commercial Asset Visibility (CAV) Repair Document Number. Use to cite the appropriate repair document number (i.e., CAV Repair Cycle Document Number or CAV-Organic Repair Module (CAV-ORM) Repair Component Document Number), depending upon applicability. CAV uses with PMR transactions. Refer to ADC 342 and ADC 461. 1/30
  527D 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. Use to cite the PQDR report control number (RCN) when applicable to the return of quality deficient/suspected quality deficient materiel and to facilitate exhibit tracking. 2. Authorized DLMS enhancement; Refer to ADC 353A and ADC 1007A. 12/12
  527D N901 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 Use in connection with the document number cited in 2/N901/30. 1/1
  527D N901 WO Work Order Number 1. For Medical use in PMR transactions to identify the Build Directive Number for medical/surgical component assembly. 2. A BDN identifies a given Build Directive. The BDN is used to identify a specific initiative to build medical sets. A first position of 1 or 2 indicates a locally established Build Directive, while a 7 or 8 indicates a DEPMEDS Build established by the Assembly Manager. A first position of 1 or 7 identifies a minor BDN, while a first position of 2 or 8 identifies a major BDN. An alpha in the first position identifies an assembly of components which were not packed on the original major BDN. 3. DLMS Component-unique enhancement. See introductory DLMS 4e. 4. A data maintenance action was approved in version 5010. The approved code/name is "BDN - Build Directive Number".
  527D N901 X9 Internal Control Number Use to identify the unique contractor reference number assigned by the contractor Contractor’s Reference Number is used to indicate the unique number used by the CAV II System to identify and track EDI transactions. Refer to ADC 342. 1/30
  527D N901 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 Navy/DLA industrial activity support agreement. Refer to ADC 381. 15/15
  527D N902
  527D N907
  527D N907-01 1Y Repair Action Number Use to identify the Depot Maintenance Inter-Service Support Agreement (DMISA) line number for tracking in-process materiel 1. Use in conjunction with N901 code AH for PMR transactions to identify the DMISA line number when tracking in-process maintenance; otherwise, do not use. 2. DLMS enhancement; see introductory DLMS note 4a. 1/30
  527D 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
  527D N907-02
Page 25  of  195 First   Previous   21  22  23  24  [25]  26  27  28  29  30  Next   Last