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
  567C G6201 BO Estimated Contract Completion Must use in unclosed CAO contract closeout extension status transactions. CAO contract closeout extension must cite the contractor in the one iteration of the 1/N1/120 loop. Do not use any transaction status indicator code. Must use when CS05 cites code D.
  567C G6201 BP Contract Closed Must use in large purchase final contract completion statements (CS05 cites code C. Must use with one iteration of 1/LQ/10 and transaction status indicator code F.
  567C G6201 BQ Extended Closeout Must use in contract closeout extension transactions (CS05 cites code E).
  567C G6201 BW Signature Use to identify the date a Responsible Official provided the notice of physical completion.
  567C G6101 RP Responsible Person
  567C 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.
  567C LQ01 0 Document Identification Code Identifies transaction specific operation to which they apply and indicates the intended purpose and use of the transaction data
  567C LQ01 10 Transaction Status Indicator Code Must use in all interim and final contract completion statements. Only use F, J, or K in LQ02. Cite code. FF - in LQ02 when CS05 cites either code A or C. Cite code J in LQ02 when CS05 cites code B. Use a contract closeout group code (i.e., when LQ01 cites code 19), when a TSI other than code K is cited in LQ02. Cite code K in LQ02 to indicate the cancelation of any type of report. 19 - Contract Close-out Group Code
  567C LQ01 25 Reason for Delayed Closing of Contract File Code For use in CAO contract closeout extension status transactions (CS05 cites code D).
  567C N101 PR Payer 1. Use to identify the disbursing Officer. 2. When this code is used, N103 must cite code M3.
  567C N101 SE Selling Party 1. Use to identify the disbursing Officer. 2. When this code is used, N103 must cite code M3.
  567C N103 33 Commercial and Government Entity (CAGE)
  567C N103 M3 Disbursing Station Use to identify the disbursing Officer by a Disbursing Station Symbol Number (DSN).
  650A ST01 650 Maintenance Service Order
  650A BGN01 0 Original Indicates the initial transaction
  650A BGN01 77 Simulation Exercise Use to identify a simulated mobilization exercise transaction set Activities initiating simulated mobilization exercises must ensure complete coordination with all activities involved. All transaction set recipients must use caution to ensure that transactions do not process as action documents which affect accountable records.
  650A BGN07 WO Work Order For Medical use in transaction for transmission of a request for assembly maintenance action.
  650A BGN08 2 Change (Update) For Medical use in transaction for transmission of a request to ad or change an assembly maintenance action.
  650A BGN08 3 Delete For Medical use in transaction for transmission of a request to delete an assembly maintenance action. Applies to Component data information.
  650A BGN08 17 Create For Medical use in transaction for initial transmission of a request for assembly maintenance action.
  650A REF01 89 Assembly Number For Medical use in transactions to identify the Unit Assembly Number for medical/surgical component assembly.
  650A REF01 IQ End Item 1. For Medical use in transactions to identify the End Item Receipt Document Number for medical/surgical component assembly. 2. End Item Receipt Document Number accommodates a DSCP requirement. The USAMA ERP does not use this data.
  650A REF01 JB Job (Project) Number For Medical use in transactions to identify the Project Order Number for medical/surgical component assembly.
  650A 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 Use to identify the customer's document number.
  650A REF01 WO Work Order Number For Medical use in transactions to identify the Build Directive Number for medical/surgical component assembly. A - data maintenance action was approved in version 5010. The approved code/name is “BDN - Build Directive Number”.
  650A DTM01 RFD Requested Finish For Medical use in transactions to identify the Build Completion Date for medical/surgical component assembly.
  650A N101 ST Ship To For Medical use in transactions to identify the assembly final destination.
  650A N101 WZ Final Maintenance Organization 1. For Medical use transactions to identify [final] assembly/maintenance organization for medical/surgical component assembly. This organization will complete kit assemblies and ship to final destination activity. 2. This qualifier represents the Assembly Activity.
  650A N101 Z4 Owning Inventory Control Point Use to indicate the source of supply 1. For Medical use in transactions to identify the supply source. 2. This qualifier represents the Assembly Manager.
  650A N103 10 Department of Defense Activity Address Code (DODAAC) Use to identify specific units, activities, and/or organizations. The first position indicates the Component or other Government element of ownership or sponsorship. The remaining five positions are assigned under established products by the Service point of the participating Component DLMS enhancement; see introductory DLMS note 3a.
  650A 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
  650A N106 FR Message From Use to identify the party originating the transaction set Use with the appropriate 1/N101/050 code to indicate that the organization cited in N104 is originating the transaction set.
  650A N106 TO Message To Use to identify the party to receive the transaction set Use with the appropriate 1/N101/050 code to indicate that the organization cited in N104 is the action organization receiving the transaction set.
  650A HL03 A Assembly For Medical use in Assemblage Control Data (DIC C2B) loop.
  650A HL03 F Component For Medical use in Component Data (DIC C2D) loop.
  650A HL03 EN End Item For Medical use in End Item Data (lDIC C2A) loop.
  650A REF01 55 Sequence Number For Medical use in Component Data lops to identify the Sort Sequence.
  650A REF01 QQ Unit Number For Medical use in Assemblage Control Data lops to identify the Assembly Control Number for medical/surgical component assembly. A - data maintenance action was approved in version 5010. The approved code/name is “CAN - Assembly Control Number”.
  650A LIN02 A3 Locally Assigned Control Number Must use with the Assemblage Control Data (C2B) loop, to identify the Assemblage Identification Number (AIN).
  650A LIN02 FS National Stock Number A number assigned under the federal cataloging program to each Approved Code United States Federal Item Identification Must use with the Component Data (C2D) loop only, to identify the stock number.
  650A LIN02 SW Stock Number Must use with the End Item Data (C2A) loop only, to identify the End Item Stock Number.
  650A LIN04 OE Original Equipment Number Use in Component Data lops to identify the Original Component Stock Number for medical/surgical component assembly.
  650A LIN06 N4 National Drug Code in 5-4-2 Format Use only to identify a National Drug Code. NSN must be identified in LIN02/03.
  650A LIN06 VC Vendor's (Seller's) Catalog Number Use only to identify the Prime Vendor's Catalog Number. NSN must be identified in LIN02/03.
  650A LIN06 VP Vendor's (Seller's) Part Number Use only to identify the Prime Vendor's Part Number. NSN must be identified in LIN02/03.
  650A QTY01 63 On Order Quantity 1. Use to identify the number of assemblies being requested, Total Number of Assemblages in End Item Data loop. 2. Use to identify the quantity of each component that is to be placed in an assembly, Basic Quantity in the Component Data loop.
  650A QTY01 AP Order Quantity Multiple Use to identify the Extended Quantity of a component part in an assembly in the Component Data loop.
  650A QTY01 SH Shortage Use to identify the Quantity Authorized Short of a component part in an assembly in the Component Data loop.
  650A QTY01 T5 Total Number of Units Use as needed in the end item data loop to identify the total number of lines in the Assemblage Identification Number (AIN).
  650A YNQ01 ZZ Mutually Defined Use in Component Data (C2D) lops to identify the Inspection Required Indicator for medical/surgical component assembly. A - data maintenance action was approved in version 5030. The approved code/name is "CAI - Component Assembly Inspection Required".
Page 32  of  141 First   Previous   28  29  30  31  [32]  33  34  35  36  37  Next   Last