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
  856S DTM01 514 Transferred 1. Use to identify the materiel transfer date to the carrier if a delay occurs prior to actual shipment. 2. DLMS enhancement; see introductory DLMS note 2a. 8/8
  856S DTM01 585 Report Use when the HL03 code W loop to identify the waste profile established date.
  856S DTM01 920 Note Use to indicate the date that items were received by the transporter Use to indicate the date that items were received by the transporter. 8/8
  856S DTM01 999 Document Date Use for CAV shipment Status to identify the ‘Proof of Shipment Date’ This date identifies the preparation date on the supporting documentation for shipment from the contractor’s plant 1. Must use for CAV shipment Status to identify the ‘Proof of Shipment Date.’ 2. This date identifies the preparation date on the supporting documentation for shipment from the contractor’s plant. 8/8
  856S DTM01 PUD Pick-Up Date Use to indicate the Manifest Pickup Date Use in HL Code MF to cite the Manifest Pickup Date. 8/8
  856S DTM02
  856S DTM03
  856S N101 BS Bill and Ship To The organization that receives both the material and the billing for goods and applicable services Use either this code, or both codes BT and ST, for reimbursable materiel. Use to identify the organization which receives both the materiel and the billing for the materiel. 3/6
  856S N101 BT Bill-to-Party The organization to receive the billing for goods and/or services Use with code ST for reimbursable materiel. Use to identify the organization to receive the billing for materiel when different from the organization receiving the materiel. Use precludes the use of Code BS. 3/6
  856S N101 CA Carrier Use as needed for directed returns to identify the carrier to be used for the return shipment 1. Use as needed to identify the shipment unit carrier when other than the United States Postal Service. 2. The carrier may be identified by name (N102) and Standard Carrier Alpha Code (SCAC). 3. Authorized DLMS migration enhancement; see introductory DLMS 2f. 1/60
  856S N101 CS Consolidator Use to identify the consolidation point Department of Defense Activity Address Code (DoDAAC) when shipment status is provided by the CCP 1. Use to identify the consolidation point DoDAAC when shipment status is provided by the CCP (BSN07=061). 2. For non-MILS shipment (e.g., DD1149) status, (BSN07=014) in support of pRFID exchange, use to identify the origin activity generating the shipment status. Refer to ADC 417. 6/6
  856S N101 DA Delivery Address Use to identify the in-the-clear exception ship-to address organization name 1. Use with 2/N2/2300, 2/N3/2400, and 2/N4/2500 to fully identify in-the-clear exception ship-to address information under authorized conditions. 2. DLMS enhancement; see introductory DLMS note 2a. 1/60
  856S 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 1. Use for transition period to support transaction conversion in a mixed legacy MILSTRIP/DLMS environment. Use to identify DAASC as originator during conversion when the legacy MILSTRIP transaction does not contain a "From" organization (i.e. blank RIC on AS_). Use to identify DAASC as the "TO" organization for Component-generated shipment status forwarded for DAAS distribution to status recipients under MILSTRIP/DLMS distribution rules (DLMS equivalent of AS8). 2. DLMS enhancement required for compliance with design/syntax. (DAASC RIC not converted for use on legacy MILSTRIP transactions). 3/3
  856S N101 HZ Hazardous Waste Generator The Department of Defense Activity Address Code (DoDAAC) of the generator turning in the waste Use when the HL03 code V loop to identify the Hazardous Material/Hazardous Waste Generator’s File Transfer DoDAAC. Use with code FR in the N106. 6/6
  856S 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/2200 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 2.a. 1/60
  856S N101 MF Manufacturer of Goods Use to identify the manufacturer of the identified item 1. Use in the shipment status loop to identify the manufacturer's name for nonstandard materiel (i.e., where part number and not NSN is used for materiel identification). 2. Use in IUID loop to identify the manufacturer of the identified item. 1/60
  856S N101 OB Ordered By Use to identify the transaction originator 1. Use to identify the requisitioner. 2. DLMS enhancement; see introductory DLMS note 2a. 1/60
  856S N101 OW Owner of Property or Unit Use to identify the property owner, material owner or owning program manager Shipping activities must use to indicate the materiel owner when the recipient will not be the new materiel owner. Authorized for all commodities and required for active UIT program items. See ADC 1244B 1/60
  856S N101 PW Pick Up Address The Department of Defense Activity Address Code (DoDAAC) at which the waste should be picked up Use when the HL03 code V loop to identify the Pickup DoDAAC. 6/6
  856S N101 RN Repair or Refurbish Location Use to identify the Commercial and Government Entity (CAGE) or Department of Defense Activity Address Code (DoDAAC) Last Repair Facility 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 344. 1/6
  856S N101 SB Storage Area Use to identify the distribution depot/storage activity 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. DoDAACs 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 299. 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 441A. 1/60
  856S N101 ST Ship To Used to identify a organization to which material is shipped as identified in the requisition or other initiating transaction 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 HM/HW shipments provide the RIC. 1/60
  856S N101 XN Planning/Maintenance Organization Use to identify the entity designated to carry Mission Support Material for distribution to End-Use shops and other customers 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. 1/3
  856S N101 Z1 Party to Receive Status 1. For shipment status forwarded for DAAS distribution to status recipients under MILSTRIP/DLMS distribution rules (AS8), the recipients will be identified on the DAAS-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/2200 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 N45112. Refer to ADC 1007. 1/60
  856S N101 Z4 Owning Inventory Control Point Use to indicate the source of supply 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 CCP/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. 1/60
  856S N101 Z5 Management Control Activity A DoD Component, DoD activity, or non-DoD activity, if participating by separate agreement (e.g., the Coast Guard), designated to receive, screen, and validate Military Service-initiated and contractor- initiated requisitions from the wholesale supply system to support DoD contracts or requirements Use for submission of all GFM requisitions. 1/60
  856S N101 Z7 Mark-for Party An entity located within the ship-to address that is to actually receive the material 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 1009A. 1/60
  856S N101 ZB Party to Receive Credit Use to identify the Business Partner Number (BPN) of the 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 299. 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. 1/60
  856S N102
  856S N103 2 Standard Carrier Alpha Code (SCAC) Use to identify the commercial carrier Use as needed to identify the commercial carrier. 4/4
  856S N103 8 UCC/EAN Global Product Identification Prefix Use to identify a company prefix assigned by an European Article Number (EAN) International numbering organization Corresponds to IAC '0-9'. 1/80
  856S N103 10 Department of Defense Activity Address Code (DODAAC) Use to identify specific units, activities, and/or organizations 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. 6/6
  856S N103 33 Commercial and Government Entity (CAGE) Use to identify establishments which either fabricates items of production and/or have design control of items procured by the federal government, or to identify certain military specifications or standards, and certain numbering systems developed by government agencies, panels or committees 5/5
  856S N103 50 Business License Number Use to identify buying or selling entities processing intragovernmental transactions 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. 9/9
  856S N103 92 Assigned by Buyer or Buyer's Agent Use to identify the user assigned Shop Service Center/Shop Store Identifier Use with N101 Code XN to identify the user assigned Shop Service Center/Shop Store Identifier. Refer to ADCs 284A, 381, and 1454. 2/80
  856S 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) 1. Use to indicate the SA structured address data. 2. DLMS enhancement; see introductory DLMS note 2a. 6/6
  856S 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
  856S 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 2.a. 2/80
  856S N104
  856S N106 FR Message From Use to identify the party originating the transaction set 1. Must use with the appropriate 2/N101/2200 code to indicate the organization cited in N104 is sending the transaction set. 2. For LRO shipment status, use with 2/N1/2200 code SB, otherwise use with code Z4 (or GP when originator not known) to indicate the organization cited in N104 is originating the transaction. 1/60
  856S 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 2.a. 1/60
  856S N106 TO Message To Use to identify the party to receive the transaction set 1. Use with the appropriate 2/N101/2200 code to indicate the organization cited in N101 is receiving the transaction set. 2. Use with 2/N1/2200 code GP (for DAASC) or Z1 to indicate the organization cited in N104 is receiving the transaction. 1/60
  856S N201
  856S N202
  856S N301
  856S N302
  856S N401
  856S N402
  856S N403
  856S N404
Page 126  of  195 First   Previous   122  123  124  125  [126]  127  128  129  130  131  Next   Last