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
  856P TD501 B Origin/Delivery Carrier (Any Mode) For WAWF Version 4.1, only Code B is valid.
  856P FOB02 OR Origin (Shipping Point) Use to identify the location where the seller hands off goods to a carrier and the buyer assumes responsibility for them 1/80
  824R NM102 6 Organization
  867I LQ01 121 Ordnance Expenditure Reason Use to provide details about the reason for the ordnance expenditure Code 121 provides details about the reason for the ordnance expenditure. 1/30
  867I PTD01 OE Ordnance Expenditure Issue (Ordnance Expenditure) – Use to identify the issue as being related to an ordnance expenditure.
  511M N101 OB Ordered By Use to identify the transaction originator Use to identify the organization that submitted the original requisition. 1/60
  511R N101 OB Ordered By Use to identify the transaction originator Use in requisitions to identify the requisitioner. 1/60
  511R N101 OB Ordered By Use to identify the transaction originator 1. Use to identify the requisitioner when the 1/N1/070 uses code ZL (Party Passing The Transaction) or Code Z5 (Management Control Activity) to identify the transaction originator. 2. DLMS enhancement: see introductory DLMS note 3a. Required entry for legacy MILSTRIP/DLMS conversion to support BSM. 3. For intra-USAF lateral requisitions, use to identify the routing identifier of the requisitioner (this is the same requisitioner identified by DoDAAC at 1/N101/070 Code OB). 1/60
  810L N101 OB Ordered By Use to identify the transaction originator 1. Use to identify the requisitioner, ordering, or turn-in activity when different from the billed activity. 2. DLMS enhancement; see introductory DLMS note 6a. 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
  867D N101 OB Ordered By Use to identify the transaction originator 1. Use to identify the requisitioner. 2. DLMS enhancement; see introductory DLMS note 4a. 1/60
  867D N101 OB Ordered By Use to identify the transaction originator Use to identify the requisitioner. 1/60
  869A N101 OB Ordered By Use to identify the transaction originator Use to identify the requisitioning activity. 1/60
  869C N101 OB Ordered By Use to identify the transaction originator Use to identify the requisitioning activity. 1/60
  869F N101 OB Ordered By Use to identify the transaction originator Must use to identify the requisitioner. 1/60
  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
  527R G6201 52 Ordered Used to indicate an order date Use in Commercial Asset Visibility (CAV) receipts to indicate an Order Date. 8/8
  527R N901 OR Order/Paragraph Number Use to identify the legacy four-position call/order number associated with the PIIN 1. For use with CAV receipt, to identify the legacy 4-position call/order number associated with a PIIN. Authorized DLMS migration enhancement for CAV use. See DLMS introductory note 5g. 2. Do not use for the PIID call/order number. Refer to ADC 1161. 4/4
  870L ST01 870 Order Status Report Organizations use this transaction set to provide status on Special Program Requirements and to notify the organization originating the transaction that the Federal Supply Classification (FSC) provided on the original transaction was incorrect. Use a single occurrence of this transaction set to transmit supply status to one or more organizations. Use one occurrence of this transaction set to transmit a single or multiple transactions. N/A
  870M ST01 870 Order Status Report Reporting organizations use this transaction set to provide supply status on open reports prior to the shipment of materiel. Organizations use this transaction set to provide disposition instructions for discrepant or deficient materiel. A single transaction set may contain a combination of transactions for standard and nonstandard materiel. N/A
  870N ST01 870 Order Status Report Country Representatives/Freight Forwarders (CRs/FFs) use this transaction set to respond to a Foreign Military Sales (FMS) Notice of Availability (NOA) providing shipment instructions for materiel reported available for shipment. N/A
  870S ST01 870 Order Status Report Organizations use this transaction set to report the current status of an entire order or a portion thereof. Use a single occurrence of this transaction set to transmit single or multiple supply status transactions to one or more organizations. N/A
  869A ST01 869 Order Status Inquiry Organizations use this transaction set to inquire about the status of or request supply assistance for previously submitted requisitions. Organizations may also use this transaction to request shipment tracing on registered insured, and certified parcel post. Use a single occurrence of this transaction set to exchange single or multiple transactions between a single activity and a single supply source. N/A
  869C ST01 869 Order Status Inquiry Organizations use this transaction set to request cancellation of previously submitted requisitions, regardless of current transaction status. Authorized organizations use this transaction to request mass or universal cancellation of requisitions. Sources of supply use this transaction to follow-up on the action taken in response to a request for mass or universal cancellation. N/A
  869F ST01 869 Order Status Inquiry Organizations use this transaction set to follow-up on the status of previously submitted requisitions. In using this transaction set, use a single occurrence of this transaction set to exchange transactions between a single activity and a single or multiple supply sources. Use one occurrence of this transaction set to transmit a single or multiple transactions. N/A
  870S DTM01 373 Order Start Use to indicate the effective date for requisitioning Use with status code CV to indicate the effective date for requisitioning. 8/8
  650A QTY01 AP Order Quantity Multiple Use to identify the Extended Quantity of a component part in an assembly in the Component Data loop Use to identify the Extended Quantity of a component part in an assembly in the Component Data loop. 1/15
  824R REF04-01 OQ Order Number Use to identify the legacy four-position call/order number associated with the PIIN or Contract Line Item Number (CLIN) 1. Use to identify the Delivery Order number associated with the CLIN in 2/REF01/020 Code C7. 2. Do not use for the PIID call/order number. The PIID call/order number is mapped to OTI02 Code CT. Refer to ADC 1161. 4/4
  856S REF04-03 OQ Order Number Use to identify the legacy four-position call/order number associated with the PIIN or Contract Line Item Number (CLIN) 1. Use for CAV shipment status to identify the Delivery Order number (REF04-01 Code CT). 2. Do not use for the PIID call/order number. The PIID call/order number is mapped to REF01, Code CT. Refer to ADC 1161A. 3. Under ADC 1014, GFP contract information is transitioned from the REF segment to the GF Segment. Delayed implementation is authorized. 4. Authorized DLMS enhancement; see introductory DLMS 2a. 4/4
  867I REF04-01 OQ Order Number Use to identify the legacy four-position call/order number associated with the PIIN or Contract Line Item Number (CLIN) 1. Use as directed by the authorizing Service/Agency in GFP-related transactions with REF01 Code CT to identify the Delivery Order number. 2. Do not use for the PIID call/order number. The PIID call/order number is mapped to REF01 Code CT. Refer to ADC 1161A. 3. Authorized DLMS enhancement. Refer to ADC 1014. 4/4
  869C REF04-01 OQ Order Number Use to identify the legacy four-position call/order number associated with the PIIN or Contract Line Item Number (CLIN) 1. Use to identify the Delivery Order number. 2. Do not use for the PIID call/order number. The PIID call/order number is mapped to REF01, Code CT. Refer to ADC 1161A. 4/4
  869C REF04-03 OQ Order Number Use to identify the legacy four-position call/order number associated with the PIIN or Contract Line Item Number (CLIN) 1. Use to identify the Delivery Order number. 2. Do not use for the PIID call/order number. The PIID call/order number is mapped to REF01, Code CT. Refer to ADC 1161A. 4/4
  869C REF04-05 OQ Order Number Use to identify the legacy four-position call/order number associated with the PIIN or Contract Line Item Number (CLIN) 1. Use to identify the Delivery Order number. 2. Do not use for the PIID call/order number. The PIID call/order number is mapped to REF01, Code CT. Refer to ADC 1161A. 4/4
  940R N907-01 OQ Order Number 1. Use in GFM-related transactions with N901 code CT to identify the legacy four-position call/order number associated with the PIIN. 2. Do not use for the PIID call/order number. The PIID call/order number is mapped to N901 Code CT. Refer to ADC 1161A. 3. Authorized DLMS enhancement; see introductory DLMS note 4a.
  511M NTE01 ORI Order Instructions Use to indicate technical/descriptive exception information Use with Requisition Exception Data Transaction (DLA DIC YRZ-Line Counters 01-20) to indicate technical/ descriptive exception information for procurement purposes. Segment may be repeated up to 20 times with same NTE01 qualifier. A maximum of 60 positions (including spaces) may be sent for each occurrence of the NTE01. A maximum of 1200 positions of text (including spaces) may be sent. Pick, pack, and special delivery type instructions (DLA DIC YRZ-Line Counters 01-06) may also be entered as exception dat a to be forwarded to a DSS storage activity, as part of an exception MRO. This type of data is limited to 360 positions (including spaces) which would be the segment repeated up to 6 times with the same NTE01 qualifier. See introductory DLMS note 3f. 1/80
  511R NTE01 ORI Order Instructions Use to indicate technical/descriptive exception information Use with Requisition Exception Data Transaction (DLA DIC YRZ-Line Counters 01-20) to indicate technical/descriptive exception information for procurement purposes. Segment may be repeated up to 20 times with same NTE01 qualifier. A maximum of 60 positions (including spaces) may be sent for each occurrence of the NTE01. A maximum of 1200 positions of text (including spaces) may be sent. Pick, pack, and special delivery type instructions (DLA DIC YRZ-Line Counters 01-06) may also be entered as exception data to be forwarded to a DSS storage activity, as part of an exception MRO. This type of data is limited to 360 positions (including spaces) which would be the segment, repeated up to 6 times, with the same NTE01 qualifier. Also used for USAF descriptive data associated with part numbered requisitions (A02/A0B rp 67-80). See introductory DLMS note 3e. 1/80
  940R NTE01 ORI Order Instructions Use to indicate technical/descriptive exception information Use to indicate pick/pack/delivery instructions. Exception information is required to be sent with accompanying exception MRO. Segment may be repeated up to 12 times with same NTE01 qualifier. Up to 360 bytes of text may be sent. A maximum of 30 bytes may be sent for each occurrence of NTE01. See introductory DLMS note 4e. 1/80
  511M QTY01 OC Order Count DLA Disposition Services uses to identify the Disposition Services Complete Container Count The complete container count will indicate how many different Disposal turn-in document (DTID)s are in the container and therefore how many different receipts are expected for a particular container DLA Disposition Services uses to identify the total number of DTIDs in a specified container (i.e., the container count) when the entire container is being requisitioned. DLMS enhancement; Refer to ADC 466. 1/9
  511R QTY01 OC Order Count DLA Disposition Services uses to identify the Disposition Services Complete Container Count The complete container count will indicate how many different Disposal turn-in document (DTID)s are in the container and therefore how many different receipts are expected for a particular container DLA Disposition Services uses to identify the Disposition Services Complete Container Count. This represents the total number of DTIDs in a specified disposition services container when the entire container is being requisitioned. DLMS enhancement; Refer to ADC466. 1/9
  527D QTY01 OC Order Count DLA Disposition Services uses to identify the Disposition Services Complete Container Count The complete container count will indicate how many different Disposal turn-in document (DTID)s are in the container and therefore how many different receipts are expected for a particular container DLA Disposition Services uses to identify the Disposition Services Complete Container Count. This represents the total number of DTIDs in a specified disposition services container, and therefore the number of receipts expected for a given container. DLMS enhancement authorized for use by DLA Disposition Services with PMRs for relocation (1/BR02/20 Transaction Type Code DE in conjunction with 2/LIN01/10 code N). 1/9
  527R QTY01 OC Order Count DLA Disposition Services uses to identify the Disposition Services Complete Container Count The complete container count will indicate how many different Disposal turn-in document (DTID)s are in the container and therefore how many different receipts are expected for a particular container DLA Disposition Services uses to identify the Disposition Services Complete Container Count. This represents the total number of DTIDs in a specified disposition services container, and therefore the number of receipts expected for a given container. DLMS enhancement authorized for use by DLA Disposition Services. 1/9
  846C QTY01 OC Order Count DLA Disposition Services uses to identify the Disposition Services Complete Container Count The complete container count will indicate how many different Disposal turn-in document (DTID)s are in the container and therefore how many different receipts are expected for a particular container DLA Disposition Services uses to identify the disposition services complete container count. This represents the total number of DTIDs in a specified disposition services container. 1/9
  940R QTY01 OC Order Count DLA Disposition Services uses to identify the Disposition Services Complete Container Count The complete container count will indicate how many different Disposal turn-in document (DTID)s are in the container and therefore how many different receipts are expected for a particular container DLA Disposition Services uses to identify the Disposition Services Complete Container Count. This represents the total number of DTIDs in a specified disposition services container. DLMS enhancement; Refer to ADC 434. 1/9
  536L HL03 O Order Use to identify the due-in asset data stratified by storage location, type of due-in, and date due for the item of supply.
  867I DTM01 938 Order Use to indicate an order date Use in commercial asset visibility (CAV). 8/8
  536L CTP02 OAP Optional to Advise Unit Price Use to indicate that the unit price is not available Use to indicate that the unit price is not available. 1/17
  511M N901 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, or to modify, 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
  511R N901 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
  527D N901 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
  527R N901 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
Page 61  of  195 First   Previous   57  58  59  60  [61]  62  63  64  65  66  Next   Last