DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 1 March 29, 2024

511 Requisition

Functional Group=RN

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Requisition Transaction Set (511) for

use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to requisition needed material and

equipment from a supply distribution system for immediate consumption or stockage against projected requirements. The originator can also

use this transaction set to inquire about the status of, amend, or terminate the original requisition.This transaction set may be used to convey a

description and quantity of the required material, delivery and billing information, and other logistics information necessary to evaluate and meet

the material needs of the originator. This transaction set is not used to establish a contractual relationship between trading partners, and may

precede the use of a purchase order.

DLMS Note:

1. Organizations use this transaction set to request the modification of previously submitted requisitions. Prior to the submission of mass

cancellation transactions, authorized organizations also use this transaction set to request mass modification of requisitions to prevent their

cancellation by the mass cancellation request. Organizations may also process this transaction set as a requisition to order items of supply

when the modification is unmatched in the Integrated Materiel Manager (IMM) system. Use a single occurrence of this transaction set to

transmit single or multiple transactions to one or more supply sources.

2. Users operating under the Defense Logistics Management Standards (DLMS) must reference the Unit of Issue and Purchase Unit

Conversion Table and Transportation Mode of Shipment Conversion Table which can be found on the Defense Enterprise Data Standards

Office (DEDSO) Web site at www.dla.mil/does/DLMS.

3. This DLMS Implementation Convention contains:

a. Data associated with a DLMS enhancement which may not be received or understood by the recipient's automated processing system. 

DLMS procedures may not have been developed.. Components must coordinate requirements and business rules with DEDSO prior to use.

b. Data associated with an Approved Change which may not have an established implementation date. This data may not be received or

understood by the recipient's automated processing system. Components must coordinate implementation with DEDSO prior to use.

c. Legacy MILSTRIP data which must be retained in the DLMS for a transition period to support transaction conversion in a mixed legacy

MILSTRIP/DLMS environment. This data will be streamlined out once full DLMS implementation is reached. Components may coordinate

with DEDSO for early termination (or retention) of specific data requirements for users operating in a full DLMS environment.

d. Data elements which have an expanded field size above existing legacy MILSTRIP capability which may not be supported by the

recipient's automated processing system. Components must coordinate implementation with DEDSO prior to use. 

e. Repetition of data (using multiple iterations or loops) which is not compatible with existing legacy MILSTRIP capability. Although

supported by the use of the ANSI X12 standard, such data is not compatible with legacy MILSTRIP/DLMS conversion and may not be

supported by the recipient's automated processing system. Components must coordinate implementation of enhanced capability with

DEDSO prior to use.

f. Data required to accommodate Component-unique transaction requirements (example: C-series transactions). Data does not apply to

legacy MILSTRIP transactions.

g. Data associated with a DLMS enhancement authorized for implementation by modernized systems under DLMS migration. This data

(including expanded field sizes) should be adopted during, or subsequent, to modernization when applicable to the Component’s business

process. Prior coordination is not required. Components should ensure that inclusion of this data in a DLMS transaction does not cause

inappropriate rejection of the transaction.

4. This transaction includes placeholders for DLMS enhancements to provide item unique identification (IUID) information pending

development of DLMS procedures and overarching OSD Supply Policy. Refer to the IUID web at URL: http://www.acq.osd.mil/dpap/pdi/uid

for DoD policy.

5. Effective April 1, 2014, refer to ADC 1075. Users must reference the GENC Standard for country codes

(https://nsgreg.nga.mil/genc/discovery) for a listing of authorized values. Under DLMS, use the GENC Digraph (two-character) code values. 

6. This revision to the DLMS IC incorporates Proposed DLMS Changes (PDCs) and Approved DLMS Changes (ADCs) listed. PDCs and

ADCs are available from the DEDSO Web site: http://www.dla.mil/HQ/InformationOperations/DLMS/eLibrary/Changes/processchanges/

 - ADC 59, Customer Identification on Automated Exception Requisitions

 - ADC 69A, DLMS Mapping to IC/DS 511M and 869F for Requisition Exception Data Transaction, DI Code YRZ 

 - ADC 75, DLA Unique Identification of Internal Customer Date in Requisitions

 - ADC 76, Air Force Unique Management Coding for NMCS/MICAP

 - ADC 77, Air Force Unique Management Coding for Materiel Management Aggregation Code (MMAC) 

 - ADC 97, Long Item Description for DMLSS Requisition Processing

1. Organizations use this transaction set to request the modification of previously submitted requisitions. Prior to the submission of mass

cancellation transactions, authorized organizations also use this transaction set to request mass modification of requisitions to prevent their

cancellation by the mass cancellation request. Organizations may also process this transaction set as a requisition to order items of supply

when the modification is unmatched in the Integrated Materiel Manager (IMM) system. Use a single occurrence of this transaction set to

transmit single or multiple transactions to one or more supply sources.

2. Users operating under the Defense Logistics Management Standards (DLMS) must reference the Unit of Issue and Purchase Unit

Conversion Table and Transportation Mode of Shipment Conversion Table which can be found on the Defense Enterprise Data Standards

Office (DEDSO) Web site at www.dla.mil/does/DLMS.

3. This DLMS Implementation Convention contains:

a. Data associated with a DLMS enhancement which may not be received or understood by the recipient's automated processing system. 

DLMS procedures may not have been developed.. Components must coordinate requirements and business rules with DEDSO prior to use.

b. Data associated with an Approved Change which may not have an established implementation date. This data may not be received or

understood by the recipient's automated processing system. Components must coordinate implementation with DEDSO prior to use.

c. Legacy MILSTRIP data which must be retained in the DLMS for a transition period to support transaction conversion in a mixed legacy

MILSTRIP/DLMS environment. This data will be streamlined out once full DLMS implementation is reached. Components may coordinate

with DEDSO for early termination (or retention) of specific data requirements for users operating in a full DLMS environment.

d. Data elements which have an expanded field size above existing legacy MILSTRIP capability which may not be supported by the

recipient's automated processing system. Components must coordinate implementation with DEDSO prior to use. 

e. Repetition of data (using multiple iterations or loops) which is not compatible with existing legacy MILSTRIP capability. Although

supported by the use of the ANSI X12 standard, such data is not compatible with legacy MILSTRIP/DLMS conversion and may not be

supported by the recipient's automated processing system. Components must coordinate implementation of enhanced capability with

DEDSO prior to use.

f. Data required to accommodate Component-unique transaction requirements (example: C-series transactions). Data does not apply to

legacy MILSTRIP transactions.

g. Data associated with a DLMS enhancement authorized for implementation by modernized systems under DLMS migration. This data

(including expanded field sizes) should be adopted during, or subsequent, to modernization when applicable to the Component’s business

process. Prior coordination is not required. Components should ensure that inclusion of this data in a DLMS transaction does not cause

inappropriate rejection of the transaction.

4. This transaction includes placeholders for DLMS enhancements to provide item unique identification (IUID) information pending

development of DLMS procedures and overarching OSD Supply Policy. Refer to the IUID web at URL: http://www.acq.osd.mil/dpap/pdi/uid

for DoD policy.

5. Effective April 1, 2014, refer to ADC 1075. Users must reference the GENC Standard for country codes

(https://nsgreg.nga.mil/genc/discovery) for a listing of authorized values. Under DLMS, use the GENC Digraph (two-character) code values. 

6. This revision to the DLMS IC incorporates Proposed DLMS Changes (PDCs) and Approved DLMS Changes (ADCs) listed. PDCs and

ADCs are available from the DEDSO Web site: http://www.dla.mil/HQ/InformationOperations/DLMS/eLibrary/Changes/processchanges/

 - ADC 59, Customer Identification on Automated Exception Requisitions

 - ADC 69A, DLMS Mapping to IC/DS 511M and 869F for Requisition Exception Data Transaction, DI Code YRZ 

 - ADC 75, DLA Unique Identification of Internal Customer Date in Requisitions

 - ADC 76, Air Force Unique Management Coding for NMCS/MICAP

 - ADC 77, Air Force Unique Management Coding for Materiel Management Aggregation Code (MMAC) 

 - ADC 97, Long Item Description for DMLSS Requisition Processing
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 2 March 29, 2024

 - ADC 169, Inclusion of Data Supporting UID of Items in DLMS Requisition and Material Release Processes

 - ADC 186, DLMS Requisition Revisions to Support Theatre Enterprise-Wide Logistics System (TEWLS)

 - ADC 221, Communication of Unit Price and Total Price under DLMS

 - ADC 221A, Revised Procedures associated with the DLMS Enhancement for Communication of Unit Price

 - ADC 243, Identification of Army Single Stock Fund (SSF) Requisitioning Actions and Edit Action Code (EAC) Authorization

 - ADC 263, Inclusion of Unit Price in Requisition Modification and Cancellation

 - ADC 264, DLMS Enhancement for Part-Numbered Requisition Format and USAF Unique Rules for Descriptive Information including

Technical Order (T.O.) Number

 - ADC 274, DLMS and DLSS Changes to Support Army Exchange Pricing

 - ADC 276, Addition of Party to Receive Copy to Support Requirements for Theater Enterprise-Wide Logistics System (TEWLS)

Requisitions

 - ADC 284, Revisions to DLMS Supplements to Add Shop Service Center (SSC) for BRAC Inventory Management and Stock Positioning

(IMSP)

 - ADC 284A, Revisions to DLMS Supplements to Add Shop Service Center (SSC) for BRAC Inventory Management and Stock Positioning

(IMSP)

 - ADC 322, Addition of Local Catalog ID qualifier to Support Requirements for Theater Enterprise-Wide Logistics System (TEWLS)

Requisitions (Supply)

 - ADC 328, “Off-Line” Requisition Processing: Internet Ordering Application Request for Component Verification of Funds Availability and

Recording of the Financial Obligation

 - ADC 352, Request for Management Code for PQDR Replacement Requisitions

 - ADC 359, Perpetuation of the Denial Management Code to the DLMS Requisition and Modification of Air Force BRAC IMSP SDR

Procedures (Supply/SDR)

 - ADC 375, New Management Code for Navy-Funded Non-Production Support Materiel Ordered under BRAC SS&D/IMSP

 - ADC 377, Transaction Copies Required for DLA Support of Navy BRAC SS&D/IMSP DLRs, Navy Program-Managed Materiel, and

Nuclear Consumable Support Materiel

 - ADC 381, Procedures and Additional Data Content supporting Requisitions, Requisition Alerts, and Unit of Use Requirements under Navy

BRAC SS&D/IMSP

 - Approved Administrative Addendum ADC 381B, Administrative Revision to Identify Delivery Location Position

 - ADC 435, DLMS Revisions for Standard Financial Information Structure (SFIS) Compliance 

 - ADC 436, Administrative Revisions to DLMS Supplements to Remove Obsolete Routing Identifier Code (RIC) “Streamline” Notes and

Update MILSTRIP/DLMS Documentation Associated with RICs (Supply/MILSTRIP/DODAAD)

 - ADC 448, Implementation of International Organization for Standardization (ISO) 3166-1 Codes for the Identification of Countries and their

Subdivisions

 - ADC 448B, Delayed implementation for International Organization for Standardization (ISO) 3166-1 Codes for the Identification of

Countries and their Subdivisions

 - ADC 466, Revised Procedures to Support Requisitioning and Transaction Exchange associated with DLA Disposition Services under

Reutilization Business Integration (RBI)

 - ADC 473, DLMS Revisions to Add the Associated Purchase Order Number in Support of the DLA Interface with the Exchange

 - ADC 473A, DLMS Revisions to Add the Associated Purchase Order Number (Supports DLA Interface with the Exchange, Navy Exchange

Service Command (NEXCOM), and Marine Corps Exchange (MCX) Non-Appropriated Funds (NAF) Activities and Non-DoD Customers)

 - ADC 1009A, DLMS Enhancements for Requisitioning to Improve Use of Mark-for Addressing, Expand Authorized Priority Designator

Validation, Correct EMALL Purchase/Credit Card Format Rules, and Require Distribution of Status for Requisitions associated with

Purchase/Credit Card Payment

 - ADC 1014, Revised Procedures for Inclusion of Contract Data in Transactions Associated with Government Furnished Property (GFP)

and Management Control Activity (MCA) Validation of Contractor Furnished Materiel (CFM) Requisitions

 - ADC 1014A, Revised Procedures for Inclusion of GFP/CFM Contract Data in DLMS Transactions – Updated Mapping for Concurrent

Identification of the Manufacturing Directive Number (MDN) and the Contract Line Item Number (CLIN)

 - ADC 1020, Inter-Service Ownership Transfer of Ammunition/ Ammunition Related Materiel

 - ADC 1023, Administrative Updates to Remove MILSTRIP References to Requisitioning from Plant Clearance Automated Reutilization

Screening System (PCARSS)

 - ADC 1043, DLMS Revisions for Department of Defense (DoD) Standard Line of Accounting (SLOA)/Accounting Classification

 - ADC 1043A, Revised Procedures for Department of Defense (DOD) Standard Line of Accounting (SLOA)/Accounting Classification to

Support Transaction Rejection Requirements

 - ADC 1043B, Revised Procedures for Department of Defense (DOD) Standard Line of Accounting (SLOA)/Accounting Classification to

Modify Business Rules for Beginning Period of Availability

 - ADC 1043C, Administrative Corrections for SLOA Data in the 810L Logistics Bill and other DLMS ICs

 - ADC 1050, New DOD EMALL DoDAAC and Supply Status Cancellation Codes for DOD EMALL Credit Card Billing

 - ADC 1068, Enhanced Procedures for Requisitioning via DOD EMALL and GSA Internet Ordering: Component Verification of Funds

Availability and Materiel Identification using the Supplier-Assigned Part Number and/or Supplier Commercial and Government Entity (CAGE)

Code

 - ADC 1075, Implementation of Geopolitical Entities, Names, and Codes (GENC) Standard by DoD Components for the Identification of

Countries and their Subdivisions.

 - Organizational Name and Other Non-Substantive (Administrative) Updates Completed on February 19, 2014

 - ADC 1110, Administrative Update to Identify Code DPC Delivery Priority Code as an Approved X12 Migration Code and Associated DLMS

Documentation; Identifies Additional Data Elements Authorized for Modification in the Requisition Modification Process

 - ADC 1123, Revised Procedures for Management Control Activity (MCA) Validation of Government Furnished Material (GFM)/Contractor

Furnished Material (CFM) Requisitions and Contractor DoDAAC Assignment

 - ADC 1136, Revise Unique Item Tracking (UIT) Procedures to support DODM 4140.01 UIT Policy and Clarify Requirements (Supply)

 - ADC 1161A, Update Uniform Procurement Instrument Identifier (PIID) Numbering System in the Federal/DLMS Implementation 

 - ADC 169, Inclusion of Data Supporting UID of Items in DLMS Requisition and Material Release Processes

 - ADC 186, DLMS Requisition Revisions to Support Theatre Enterprise-Wide Logistics System (TEWLS)

 - ADC 221, Communication of Unit Price and Total Price under DLMS

 - ADC 221A, Revised Procedures associated with the DLMS Enhancement for Communication of Unit Price

 - ADC 243, Identification of Army Single Stock Fund (SSF) Requisitioning Actions and Edit Action Code (EAC) Authorization

 - ADC 263, Inclusion of Unit Price in Requisition Modification and Cancellation

 - ADC 264, DLMS Enhancement for Part-Numbered Requisition Format and USAF Unique Rules for Descriptive Information including

Technical Order (T.O.) Number

 - ADC 274, DLMS and DLSS Changes to Support Army Exchange Pricing

 - ADC 276, Addition of Party to Receive Copy to Support Requirements for Theater Enterprise-Wide Logistics System (TEWLS)

Requisitions

 - ADC 284, Revisions to DLMS Supplements to Add Shop Service Center (SSC) for BRAC Inventory Management and Stock Positioning

(IMSP)

 - ADC 284A, Revisions to DLMS Supplements to Add Shop Service Center (SSC) for BRAC Inventory Management and Stock Positioning

(IMSP)

 - ADC 322, Addition of Local Catalog ID qualifier to Support Requirements for Theater Enterprise-Wide Logistics System (TEWLS)

Requisitions (Supply)

 - ADC 328, “Off-Line” Requisition Processing: Internet Ordering Application Request for Component Verification of Funds Availability and

Recording of the Financial Obligation

 - ADC 352, Request for Management Code for PQDR Replacement Requisitions

 - ADC 359, Perpetuation of the Denial Management Code to the DLMS Requisition and Modification of Air Force BRAC IMSP SDR

Procedures (Supply/SDR)

 - ADC 375, New Management Code for Navy-Funded Non-Production Support Materiel Ordered under BRAC SS&D/IMSP

 - ADC 377, Transaction Copies Required for DLA Support of Navy BRAC SS&D/IMSP DLRs, Navy Program-Managed Materiel, and

Nuclear Consumable Support Materiel

 - ADC 381, Procedures and Additional Data Content supporting Requisitions, Requisition Alerts, and Unit of Use Requirements under Navy

BRAC SS&D/IMSP

 - Approved Administrative Addendum ADC 381B, Administrative Revision to Identify Delivery Location Position

 - ADC 435, DLMS Revisions for Standard Financial Information Structure (SFIS) Compliance 

 - ADC 436, Administrative Revisions to DLMS Supplements to Remove Obsolete Routing Identifier Code (RIC) “Streamline” Notes and

Update MILSTRIP/DLMS Documentation Associated with RICs (Supply/MILSTRIP/DODAAD)

 - ADC 448, Implementation of International Organization for Standardization (ISO) 3166-1 Codes for the Identification of Countries and their

Subdivisions

 - ADC 448B, Delayed implementation for International Organization for Standardization (ISO) 3166-1 Codes for the Identification of

Countries and their Subdivisions

 - ADC 466, Revised Procedures to Support Requisitioning and Transaction Exchange associated with DLA Disposition Services under

Reutilization Business Integration (RBI)

 - ADC 473, DLMS Revisions to Add the Associated Purchase Order Number in Support of the DLA Interface with the Exchange

 - ADC 473A, DLMS Revisions to Add the Associated Purchase Order Number (Supports DLA Interface with the Exchange, Navy Exchange

Service Command (NEXCOM), and Marine Corps Exchange (MCX) Non-Appropriated Funds (NAF) Activities and Non-DoD Customers)

 - ADC 1009A, DLMS Enhancements for Requisitioning to Improve Use of Mark-for Addressing, Expand Authorized Priority Designator

Validation, Correct EMALL Purchase/Credit Card Format Rules, and Require Distribution of Status for Requisitions associated with

Purchase/Credit Card Payment

 - ADC 1014, Revised Procedures for Inclusion of Contract Data in Transactions Associated with Government Furnished Property (GFP)

and Management Control Activity (MCA) Validation of Contractor Furnished Materiel (CFM) Requisitions

 - ADC 1014A, Revised Procedures for Inclusion of GFP/CFM Contract Data in DLMS Transactions – Updated Mapping for Concurrent

Identification of the Manufacturing Directive Number (MDN) and the Contract Line Item Number (CLIN)

 - ADC 1020, Inter-Service Ownership Transfer of Ammunition/ Ammunition Related Materiel

 - ADC 1023, Administrative Updates to Remove MILSTRIP References to Requisitioning from Plant Clearance Automated Reutilization

Screening System (PCARSS)

 - ADC 1043, DLMS Revisions for Department of Defense (DoD) Standard Line of Accounting (SLOA)/Accounting Classification

 - ADC 1043A, Revised Procedures for Department of Defense (DOD) Standard Line of Accounting (SLOA)/Accounting Classification to

Support Transaction Rejection Requirements

 - ADC 1043B, Revised Procedures for Department of Defense (DOD) Standard Line of Accounting (SLOA)/Accounting Classification to

Modify Business Rules for Beginning Period of Availability

 - ADC 1043C, Administrative Corrections for SLOA Data in the 810L Logistics Bill and other DLMS ICs

 - ADC 1050, New DOD EMALL DoDAAC and Supply Status Cancellation Codes for DOD EMALL Credit Card Billing

 - ADC 1068, Enhanced Procedures for Requisitioning via DOD EMALL and GSA Internet Ordering: Component Verification of Funds

Availability and Materiel Identification using the Supplier-Assigned Part Number and/or Supplier Commercial and Government Entity (CAGE)

Code

 - ADC 1075, Implementation of Geopolitical Entities, Names, and Codes (GENC) Standard by DoD Components for the Identification of

Countries and their Subdivisions.

 - Organizational Name and Other Non-Substantive (Administrative) Updates Completed on February 19, 2014

 - ADC 1110, Administrative Update to Identify Code DPC Delivery Priority Code as an Approved X12 Migration Code and Associated DLMS

Documentation; Identifies Additional Data Elements Authorized for Modification in the Requisition Modification Process

 - ADC 1123, Revised Procedures for Management Control Activity (MCA) Validation of Government Furnished Material (GFM)/Contractor

Furnished Material (CFM) Requisitions and Contractor DoDAAC Assignment

 - ADC 1136, Revise Unique Item Tracking (UIT) Procedures to support DODM 4140.01 UIT Policy and Clarify Requirements (Supply)

 - ADC 1161A, Update Uniform Procurement Instrument Identifier (PIID) Numbering System in the Federal/DLMS Implementation 
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 3 March 29, 2024

Conventions and DLMS Manuals

 - ADC 1176, Revised Procedures for Requisitioning under Inter-Service Maintenance Agreement (Project Codes 3AB, 3AD, 3BB) and

Revised DLMS 832N Catalog Data Support for Defense Logistics Agency (DLA) support of Navy Fleet Readiness Centers (FRCs)

 - ADC 1184, Removal of the Internal Order Number from the 511R Requisition Submitted via FEDMALL

- Administrative Update to Reflect Realignment to Recognize DLMS Program Office Completed on December 15, 2016

- ADC 1287, DLMS Implementation Convention (IC) Revisions for Data Element Mapping (Form Stock Number and Manufacturer's Part

Number), Removal of Plant Equipment Number, and Administrative Updates

- ADC 1306, Carrier Identification and In-Transit Visibility Enhancements for the Federal Emergency Management Agency (FEMA)

- ADC 1307, Update Requisition-Related DLMS Transactions to Include GS1 Barcode Information for the Navy Exchange Service

Command (NEXCOM)

- ADC 1307A, Add Global Trade Item Number (GTIN) Identifiers to the DLMS 810L Logistics Bill for Non-Appropriated Fund Activities and

Non-DoD Customers

- Administrative Update to Reflect Realignment of DLMS Program Office to Enterprise Business Standards Office (EBSO) - Completed on

October 22, 2018

- ADC 1321, Revise DLMS Requisition-Related Transactions to Include Customer Point of Contact Information

- ADC 1343, Missing Materiel Receipt Acknowledgement (MRA) Closeout (Supply)

- ADC 1360, Remove References to Disposal Condition Codes in DLA 4000.25 and DLMS Transactions 511M, 511R, and 869F

- ADC 1367, Administrative Update to Convert Federal Notes to DLMS Notes within DLMS Implementation Conventions 

- ADC 1370, Administrative Update to Change Data Element N106 Usage from Must Use to Used

- ADC 1381, Administrative Update to DLMS 511M Requisition Modification and 511R Requisition to Remove Reference to Foreign Military

Sales Transportation Costs

- ADC 1390, Use of Management Codes in DLMS 511R Requisition, 511M Requisition Modification and 869F Requisition Follow-Up

(Supply)

- Administrative Update to Reflect Realignment of Enterprise Business Standards Office (EBSO) to Defense Enterprise Data Standards

Office (DEDSO) - Completed on October 27, 2021

- ADC 1412, Replacement of Data Universal Numbering System Number with Unique Entity Identifier and Electronic Funds Transfer

Indicator to Wide Area Workflow

- ADC 1420, Other Transaction (OT) Agreements Instrument Type and Procurement Instrument Identifier (PIID) Construct (Supply/Contract

Administration)

- ADC 1454, Expand Use of Shop Service Center Codes in Defense Logistics Management Standards Transactions

- ADC 1465, G-Invoicing Federal Intragovernmental Data Standards

Conventions and DLMS Manuals

 - ADC 1176, Revised Procedures for Requisitioning under Inter-Service Maintenance Agreement (Project Codes 3AB, 3AD, 3BB) and

Revised DLMS 832N Catalog Data Support for Defense Logistics Agency (DLA) support of Navy Fleet Readiness Centers (FRCs)

 - ADC 1184, Removal of the Internal Order Number from the 511R Requisition Submitted via FEDMALL

- Administrative Update to Reflect Realignment to Recognize DLMS Program Office Completed on December 15, 2016

- ADC 1287, DLMS Implementation Convention (IC) Revisions for Data Element Mapping (Form Stock Number and Manufacturer's Part

Number), Removal of Plant Equipment Number, and Administrative Updates

- ADC 1306, Carrier Identification and In-Transit Visibility Enhancements for the Federal Emergency Management Agency (FEMA)

- ADC 1307, Update Requisition-Related DLMS Transactions to Include GS1 Barcode Information for the Navy Exchange Service

Command (NEXCOM)

- ADC 1307A, Add Global Trade Item Number (GTIN) Identifiers to the DLMS 810L Logistics Bill for Non-Appropriated Fund Activities and

Non-DoD Customers

- Administrative Update to Reflect Realignment of DLMS Program Office to Enterprise Business Standards Office (EBSO) - Completed on

October 22, 2018

- ADC 1321, Revise DLMS Requisition-Related Transactions to Include Customer Point of Contact Information

- ADC 1343, Missing Materiel Receipt Acknowledgement (MRA) Closeout (Supply)

- ADC 1360, Remove References to Disposal Condition Codes in DLA 4000.25 and DLMS Transactions 511M, 511R, and 869F

- ADC 1367, Administrative Update to Convert Federal Notes to DLMS Notes within DLMS Implementation Conventions 

- ADC 1370, Administrative Update to Change Data Element N106 Usage from Must Use to Used

- ADC 1381, Administrative Update to DLMS 511M Requisition Modification and 511R Requisition to Remove Reference to Foreign Military

Sales Transportation Costs

- ADC 1390, Use of Management Codes in DLMS 511R Requisition, 511M Requisition Modification and 869F Requisition Follow-Up

(Supply)

- Administrative Update to Reflect Realignment of Enterprise Business Standards Office (EBSO) to Defense Enterprise Data Standards

Office (DEDSO) - Completed on October 27, 2021

- ADC 1412, Replacement of Data Universal Numbering System Number with Unique Entity Identifier and Electronic Funds Transfer

Indicator to Wide Area Workflow

- ADC 1420, Other Transaction (OT) Agreements Instrument Type and Procurement Instrument Identifier (PIID) Construct (Supply/Contract

Administration)

- ADC 1454, Expand Use of Shop Service Center Codes in Defense Logistics Management Standards Transactions

- ADC 1465, G-Invoicing Federal Intragovernmental Data Standards

Heading:

Pos Id Segment Name Req Max Use Repeat Notes Usage

10 ST Transaction Set Header M 1 Must use

20 BR Beginning Segment for Material

Management

M 1 Must use

30 G62 Date/Time O 10 Used

* 40 NTE Note/Special Instruction O 10 Not Used

LOOP ID - LM LOOP ID - LM 50 N1/50L

50 LM Code Source Information O 1 N1/50 Used

60 LQ Industry Code M 100 Must use

LOOP ID - N1 LOOP ID - N1 20 N1/70L

70 N1 Name M 1 N1/70 Must use

* 80 N2 Additional Name Information O 2 Not Used

* 90 N3 Address Information O 2 Not Used

* 100 N4 Geographic Location O 1 Not Used

110 G61 Contact O 5 Used

Detail:

Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - LX LOOP ID - LX >1

10 LX Assigned Number O 1 Used

20 N9 Reference Identification M >1 Must use

30 PO1 Baseline Item Data O >1 Used

* 50 PWK Paperwork O 1 Not Used

60 DD Demand Detail O 100 Used

70 GF Furnished Goods and Services O 1 Used

80 G62 Date/Time O 20 Used
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Pos Id Segment Name Req Max Use Repeat Notes Usage

004010F511M5MA56 4 March 29, 2024

* 90 MAN Marks and Numbers O 5 Not Used

100 LIN Item Identification O >1 Used

105 MEA Measurements O >1 Used

110 G69 Line Item Detail - Description O >1 Used

120 NTE Note/Special Instruction O >1 Used

LOOP ID - LM LOOP ID - LM 50

130 LM Code Source Information O 1 Used

140 LQ Industry Code M 100 Must use

LOOP ID - QTY LOOP ID - QTY >1 N2/150L N2/150L

150 QTY Quantity O 1 N2/150 Used

* LOOP ID - LM * LOOP ID - LM 50

160 LM Code Source Information O 1 Used

170 LQ Industry Code M 100 Must use

LOOP ID - N1 LOOP ID - N1 100 N2/180L N2/180L

180 N1 Name O 1 N2/180 Used

190 N2 Additional Name Information O 2 Used

200 N3 Address Information O 2 Used

210 N4 Geographic Location O 1 Used

* 215 G61 Contact O 5 Not Used

LOOP ID - REF LOOP ID - REF >1 N2/220L N2/220L

220 REF Reference Identification O 1 N2/220 Used

* 230 G62 Date/Time O 10 Not Used

240 N9 Reference Identification O >1 Used

250 N1 Name O 1 Used

* 260 R4 Port or Terminal O 1 Not Used

* LOOP ID - LM * LOOP ID - LM 50

* 270 LM Code Source Information O 1 Not Used

280 LQ Industry Code M 100 Must use

LOOP ID - FA1 LOOP ID - FA1 >1

285 FA1 Type of Financial Accounting Data O 1 Used

286 FA2 Accounting Data M >1 Must use

290 SE Transaction Set Trailer M 1 Must use

Notes: 

1/50L The LM loop identifies logistic data common to the entire transaction set.

1/50 The LM loop identifies logistic data common to the entire transaction set.

1/70L The N1 loop identifies name and or address information common to the entire transaction set.

1/70 The N1 loop identifies name and or address information common to the entire transaction set.

2/150L Each iteration of the QTY loop qualifies a portion of the total quantity ordered with particular logistics information codes.

2/150 Each iteration of the QTY loop qualifies a portion of the total quantity ordered with particular logistics information codes.

2/180L The N1 loop identifies the name and address information unique to each use of the LX loop.

2/180 The N1 loop identifies the name and address information unique to each use of the LX loop.

2/220L The REF loop conveys serial and lot number inventory data.

2/220 The REF loop conveys serial and lot number inventory data.
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 5 March 29, 2024

ST Transaction Set Header Pos: 10 Max: 1

Heading - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must use

Purpose: To indicate the start of a transaction set and to assign a control number

Semantics: 

1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set

definition (e.g., 810 selects the Invoice Transaction Set).

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

ST01 143 Transaction Set Identifier Code

Description: Code uniquely identifying a

Transaction Set

M ID 3/3 Must use

Code Name

511 Requisition

ST02 329 Transaction Set Control Number

Description: Identifying control number that must

be unique within the transaction set functional group

assigned by the originator for a transaction set

DLMS Note: A unique number assigned by the

originator of the transaction set, or the originator's

application program.

M AN 4/9 Must use
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 6 March 29, 2024

BR Beginning Segment for Material

Management

Pos: 20 Max: 1

Heading - Mandatory

Loop: N/A Elements: 7

User Option (Usage): Must use

Purpose: To indicate the beginning of a material management transaction and transmit identifying numbers and dates

Syntax Rules: 

1. C0504 - If BR05 is present, then BR04 is required.

2. P0708 - If either BR07 or BR08 is present, then the other is required.

3. P1011 - If either BR10 or BR11 is present, then the other is required.

Semantics: 

1. BR03 is the date of the transaction set preparation.

2. BR09 is the time of the transaction set preparation

DLMS Note:

1. Use table 1 and 2 to request modification of individual transactions.

2. Use table 1 and only 2/SE/290 to request a mass modification.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

BR01 353 Transaction Set Purpose Code

Description: Code identifying purpose of

transaction set

M ID 2/2 Must use

Code Name

00 Original

77 Simulation Exercise

DLMS Note:

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 extreme caution to ensure that individual transactions do not process as action

documents which affect accountable records.

ZZ Mutually Defined

DLMS Note:

1. Use to identify the Unit of Use Indicator. When included, the quantity and unit of measure values

associated with this transaction are applicable to the unit of use. 

2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

BR02 640 Transaction Type Code

Description: Code specifying the type of

transaction

M ID 2/2 Must use

Code Name

AM Requisition Modification

DLMS Note:

Use to indicate the transaction set contains one or more modifications. Transaction set recipients may

process as a requisition when no record of original requisition exists in the IMM's system.

BR03 373 Date

Description: Date expressed as CCYYMMDD

DLMS Note: This date corresponds to the Universal

Time Coordinate (UTC).

M DT 8/8 Must use
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004010F511M5MA56 7 March 29, 2024

BR04 67 Identification Code

Description: Code identifying a party or other code

X AN 2/80 Used

BR05 66 Identification Code Qualifier

Description: Code designating the system/method

of code structure used for Identification Code (67)

O ID 1/2 Used

Code Name

10 Department of Defense Activity Address Code (DODAAC)

DLMS Note:

Use only to identify the organization to which a mass modification is applicable.

A2 Military Assistance Program Address Code (MAPAC)

DLMS Note:

Use to indicate the Security Assistance (SA) structured address data. 

BR06 306 Action Code

Description: Code indicating type of action

DLMS Note: 1. Use only when the transaction set

contains a request for mass modification of

requisitions.

2. When used, the transaction set identifies

requisitions associated with an organization

(identified in 1/BR/020). The range of requisitions

may be qualified through the identification of a

series of project codes, special requirements codes

or priorities (identified in the 1/LM/050 loop) and/or a

range of transaction number dates (identified in

1/G62/030).

2. When used, the transaction set identifies

requisitions associated with an organization

(identified in 1/BR/020). The range of requisitions

may be qualified through the identification of a

series of project codes, special requirements codes

or priorities (identified in the 1/LM/050 loop) and/or a

range of transaction number dates (identified in

1/G62/030).

O ID 1/2 Used

Code Name

2 Change (Update)

DLMS Note:

Use for mass modifications to indicate that Special Requirements Code 555 should be assigned to all

requisitions that should not be canceled by a mass cancellation transaction.

83 Future

DLMS Note:

1. Used by Navy industrial activities (IAs) to identify a Requisition Alert allowing stock positioning or

procurement action in response to the forecasted future funded requirement. The requisition alert is an

unfunded requirement. 

2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

FI File

DLMS Note:

1. Use with BR02 Code AM to identify a requisition modification image transaction. All transaction set

recipients must use extreme caution to ensure that individual transactions do not process as action

documents which affect accountable records.

2. Used on image transactions provided to DLA for Navy requisitions submitted directly to other

Component SoS, so that DLA will be able to support follow-on actions on behalf of the Navy industrial

activity (IA) under a DLA industrial activity support agreement. Refer to ADC 377.

1. Use with BR02 Code AM to identify a requisition modification image transaction. All transaction set

recipients must use extreme caution to ensure that individual transactions do not process as action

documents which affect accountable records.

2. Used on image transactions provided to DLA for Navy requisitions submitted directly to other

Component SoS, so that DLA will be able to support follow-on actions on behalf of the Navy industrial

activity (IA) under a DLA industrial activity support agreement. Refer to ADC 377.

BR09 337 Time

Description: Time expressed in 24-hour clock time

as follows: HHMM, or HHMMSS, or HHMMSSD, or

HHMMSSDD, where H = hours (00-23), M = minutes

(00-59), S = integer seconds (00-59) and DD =

decimal seconds; decimal seconds are expressed

as follows: D = tenths (0-9) and DD = hundredths

O TM 4/8 Must use
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004010F511M5MA56 8 March 29, 2024

(00-99)

DLMS Note: 1. Express the originating activity's

time in UTC.

2. Express time in a four-position (HHMM) format.
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 9 March 29, 2024

G62 Date/Time Pos: 30 Max: 10

Heading - Optional

Loop: N/A Elements: 2

User Option (Usage): Used

Purpose: To specify pertinent dates and times

Syntax Rules: 

1. R0103 - At least one of G6201 or G6203 is required.

2. P0102 - If either G6201 or G6202 is present, then the other is required.

3. P0304 - If either G6203 or G6204 is present, then the other is required.

DLMS Note:

1. Use in mass modification transactions to identify a range of requisition transaction number dates for which mass modification applies.

2. Use in mass modification transactions for ammunition items to identify the required delivery period.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

G6201 432 Date Qualifier

Description: Code specifying type of date

X ID 2/2 Must use

Code Name

53 Deliver Not Before Date

DLMS Note:

For conventional ammunition, use to indicate the required delivery period start date, inclusive.

54 Deliver No Later Than Date

DLMS Note:

For conventional ammunition, use to indicate the required delivery period end date, inclusive.

62 Accrual Start Date

DLMS Note:

Use to indicate the range start date, inclusive.

63 Accrual End Date

DLMS Note:

Use to indicate the range stop date, inclusive.

G6202 373 Date

Description: Date expressed as CCYYMMDD

X DT 8/8 Must use
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 10 March 29, 2024

LM Code Source Information Pos: 50 Max: 1

Heading - Optional

Loop: LM Elements: 1

User Option (Usage): Used

Purpose: To transmit standard code list identification information

Comments: 

1. LM02 identifies the applicable industry code list source information.

DLMS Note:

Use this 1/LM/050 loop only in mass modification transactions to identify the applicable codes which further define the range of transactions

to which this transaction set applies.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

LM01 559 Agency Qualifier Code

Description: Code identifying the agency assigning

the code values

M ID 2/2 Must use

Code Name

DF Department of Defense (DoD)
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 11 March 29, 2024

LQ Industry Code Pos: 60 Max: 100

Heading - Mandatory

Loop: LM Elements: 2

User Option (Usage): Must use

Purpose: Code to transmit standard industry codes

Syntax Rules: 

1. C0102 - If LQ01 is present, then LQ02 is required.

DLMS Note:

Use to identify codes, as appropriate, consistent with management information requirements.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

LQ01 1270 Code List Qualifier Code

Description: Code identifying a specific industry

code list

DLMS Note: The following codes are authorized.

O ID 1/3 Must use

Code Name

78 Project Code

79 Priority Designator Code

AL Special Requirements Code

DLMS Note:

1. Use to identify precedence, special handling, and processing requirements.

2. Under legacy MILSTRIP, this is carried in the required delivery date field. 

3. DLMS enhancement; see introductory DLMS note 3a.

LQ02 1271 Industry Code

Description: Code indicating a code from a specific

industry code list

X AN 1/30 Must use
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 12 March 29, 2024

N1 Name Pos: 70 Max: 1

Heading - Mandatory

Loop: N1 Elements: 4

User Option (Usage): Must use

Purpose: To identify a party by type of organization, name, and code

Syntax Rules: 

1. R0203 - At least one of N102 or N103 is required.

2. P0304 - If either N103 or N104 is present, then the other is required.

Comments: 

1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID

Code" (N104) must provide a key to the table maintained by the transaction processing party.

2. N105 and N106 further define the type of entity in N101.

DLMS Note:

1. Must use this 1/N1/070 loop to identify the organization originating the transaction set.

2. Use additional iterations of this 1/N1/070 loop to identify the supply source for mass modifications and for all Government Furnished

Materiel (GFM) transactions.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

N101 98 Entity Identifier Code

Description: Code identifying an organizational

entity, a physical location, property or an individual

DLMS Note: The following codes are authorized.

M ID 2/3 Must use

Code Name

GP Gateway Provider

DLMS Note:

Use for transition period to support transaction conversion in a mixed legacy MILSTRIP/DLMS

environment. Use to identify Transaction Services as originator during conversion when legacy

MILSTRIP transaction does not contain a "From" organization.

OB Ordered By

DLMS Note:

Use to identify the organization that submitted the original requisition.

UK System

DLMS Note:

Use to identify the originating system Communications Routing Identifier (COMMRI).

Z4 Owning Inventory Control Point

DLMS Note:

Use only in mass modifications to identify the supply source.

Z5 Management Control Activity

DLMS Note:

1. Use in mass modifications to identify the MCA for all Government Furnished Materiel (GFM)

transactions.

2. Use in GFM or CFM requisition modifications forwarded to the source of supply by the MCA.

N103 66 Identification Code Qualifier

Description: Code designating the system/method

of code structure used for Identification Code (67)

X ID 1/2 Must use
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 13 March 29, 2024

Code Name

10 Department of Defense Activity Address Code (DODAAC)

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

A2 Military Assistance Program Address Code (MAPAC)

DLMS Note:

Use to indicate the Security Assistance (SA) structured address data.

C4 Department of Defense Communication Routing Identifier (COMMRI)

DLMS Note:

1. Use only when N101 is UK.

2. At this time a local code C4 is established for use in 511M version 4010. A data maintenance action

was submitted to ASC X12 to establish C4 Department of Defense Communication Routing Identifier

(COMMRI) in a future version.

M4 Department of Defense Routing Identifier Code (RIC)

N104 67 Identification Code

Description: Code identifying a party or other code

X AN 2/80 Must use

N106 98 Entity Identifier Code

Description: Code identifying an organizational

entity, a physical location, property or an individual

O ID 2/3 Used

Code Name

FR Message From

DLMS Note:

1. Must use with the appropriate 1/N101/070 code to indicate the organization cited in N104 is

originating the transaction set.

2. Must use with the 1/N101/070 code OB or Z5.

TO Message To

DLMS Note:

1. Use only in mass modifications with the appropriate 1/N101/070 code to indicate that the organization

cited in N104 is receiving the transaction set.

2. Use only in mass modifications with 1/N101/070 code Z4 or Z5.
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 14 March 29, 2024

G61 Contact Pos: 110 Max: 5

Heading - Optional

Loop: N1 Elements: 5

User Option (Usage): Used

Purpose: To identify a person or office to whom communications should be directed

Syntax Rules: 

1. P0304 - If either G6103 or G6104 is present, then the other is required.

Comments: 

1. G6103 qualifies G6104.

DLMS Note:

1. Use in other than mass modifications and under exceptional circumstances when requiring direct communication with the party originating

the transaction set.

2. Use multiple repetitions to identify multiple points of contact or communication numbers. When using multiple repetitions to identify

different communication numbers for a single point of contact, repeat the name cited in G6102.

3. Use for General Services Administration (GSA) requisitions. Refer to ADC 1321.

4. DLMS enhancement; see introductory DLMS note 3a.

1. Use in other than mass modifications and under exceptional circumstances when requiring direct communication with the party originating

the transaction set.

2. Use multiple repetitions to identify multiple points of contact or communication numbers. When using multiple repetitions to identify

different communication numbers for a single point of contact, repeat the name cited in G6102.

3. Use for General Services Administration (GSA) requisitions. Refer to ADC 1321.

4. DLMS enhancement; see introductory DLMS note 3a.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

G6101 366 Contact Function Code

Description: Code identifying the major duty or

responsibility of the person or group named

M ID 2/2 Must use

Code Name

AA Authorized Representative

IC Information Contact

DLMS Note:

1. Use to identify the point of contact. Refer to ADC 1321.

2. DLA Disposition Services uses in conjunction with the Ordered By DoDAAC to perpetuate the

customer contact name and phone number from the Reutilization/Transfer/Donation (RTD) Web

Application to DLA Disposition Services. Refer to ADC 466.

G6102 93 Name

Description: Free-form name

DLMS Note: Use a job title or description instead of

an individual’s name if security or privacy concerns

do not permit the use of a name. Refer to ADC

1321.

M AN 1/60 Must use

G6103 365 Communication Number Qualifier

Description: Code identifying the type of

communication number

DLMS Note: 1. Use to identify the preferred method

of communication in the first repetition. Use

additional repetitions when identifying alternate

communication methods.

2. Do not include blank spaces, dashes or

parenthesis between numbers.

3. Use to provide a commercial phone number

and/or e-mail address to facilitate carrier deliveries 

X ID 2/2 Must use
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004010F511M5MA56 15 March 29, 2024

or source of supply inquiries. Refer to ADC 1321.

Code Name

AU Defense Switched Network

DLMS Note:

Use to identify the DSN telephone number.

EM Electronic Mail

EX Telephone Extension

DLMS Note:

Use immediately following codes AU, IT, or TE to identify a telephone extension.

FX Facsimile

DLMS Note:

Use to identify the facsimile (FAX) telephone number.

IT International Telephone

DLMS Note:

Include country and city code.

TE Telephone

DLMS Note:

Use to identify a commercial phone number. Include the area code and number.

TL Telex

TX TWX

G6104 364 Communication Number

Description: Complete communications number

including country or area code when applicable

DLMS Note: Do not include blank spaces, dashes

or parenthesis between numbers.

X AN 1/80 Must use

G6105 443 Contact Inquiry Reference

Description: Additional reference number or

description to clarify a contact number

DLMS Note: Use to indicate the office symbol or

activity code for the party identified.

O AN 1/20 Used
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 16 March 29, 2024

LX Assigned Number Pos: 10 Max: 1

Detail - Optional

Loop: LX Elements: 1

User Option (Usage): Used

Purpose: To reference a line number in a transaction set

DLMS Note:

1. Use for individual modification transactions as a counter to identify the number of 2/LX/010 loop iterations in the transaction set.

2. Do not use this or any table 2 segments, except 2/SE/290, for mass modifications.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

LX01 554 Assigned Number

Description: Number assigned for differentiation

within a transaction set

DLMS Note: In the first 2/LX/010 loop iteration, cite

numeric 1. In each subsequent loop iteration,

increase incrementally by 1.

M N0 1/6 Must use
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 17 March 29, 2024

N9 Reference Identification Pos: 20 Max: >1

Detail - Mandatory

Loop: LX Elements: 4

User Option (Usage): Must use

Purpose: To transmit identifying information as specified by the Reference Identification Qualifier

Syntax Rules: 

1. R0203 - At least one of N902 or N903 is required.

2. C0605 - If N906 is present, then N905 is required.

Semantics: 

1. N906 reflects the time zone which the time reflects.

2. N907 contains data relating to the value cited in N902.

DLMS Note:

1. Must use in individual transactions to identify the transaction number of the requisition to be modified. 

2. Use additional repetitions to identify ancillary information related to the transaction.

3. The composition of each transaction number within the 511 transaction set is as follows: (1) the DoDAAC (or Security Assistance (SA)

identification data, (2) a four position date consisting of the last digit of the calendar year and the ordinal day of the calendar year, and (3)

the requisition serial number.

4. For Military Assistance Program/Grant Aid (MAP/GA) transactions, the SA identification data is a six position number consisting of Service

Assignment Code in the first position, Country or International Organization Code in the second and third positions,

Customer-Within-Country Code in the fourth position, zero in the fifth position, and Type of Assistance and Financing Code in the sixth

position. 

5. For Foreign Military Sales (FMS) transactions, the SA identification data is a six position number consisting of Service Assignment Code

in the first position, Country or International Organization Code in the second and third positions, Customer-Within-Country Code in the

fourth position, Delivery Terms Code in the fifth position, and Type of Assistance and Financing Code in the sixth position. For Canada only,

identify the customer-within-country with a two position code in the fourth and fifth positions.

6. Do not repeat the SA identification addressing information elsewhere in the transaction set.

1. Must use in individual transactions to identify the transaction number of the requisition to be modified. 

2. Use additional repetitions to identify ancillary information related to the transaction.

3. The composition of each transaction number within the 511 transaction set is as follows: (1) the DoDAAC (or Security Assistance (SA)

identification data, (2) a four position date consisting of the last digit of the calendar year and the ordinal day of the calendar year, and (3)

the requisition serial number.

4. For Military Assistance Program/Grant Aid (MAP/GA) transactions, the SA identification data is a six position number consisting of Service

Assignment Code in the first position, Country or International Organization Code in the second and third positions,

Customer-Within-Country Code in the fourth position, zero in the fifth position, and Type of Assistance and Financing Code in the sixth

position. 

5. For Foreign Military Sales (FMS) transactions, the SA identification data is a six position number consisting of Service Assignment Code

in the first position, Country or International Organization Code in the second and third positions, Customer-Within-Country Code in the

fourth position, Delivery Terms Code in the fifth position, and Type of Assistance and Financing Code in the sixth position. For Canada only,

identify the customer-within-country with a two position code in the fourth and fifth positions.

6. Do not repeat the SA identification addressing information elsewhere in the transaction set.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

N901 128 Reference Identification Qualifier

Description: Code qualifying the Reference

Identification

DLMS Note: 1. Supply sources only use one of

codes CT or W4 to advise a procurement activity of

the contract or procurement request (PR)

information.

2. The following codes are authorized.

M ID 2/3 Must use

Code Name

60 Account Suffix Code

DLMS Note:

Use in conjunction with the DTID Number (N907 Code W1) to identify the DTID Number Suffix Code,

when applicable. DLMS enhancement, see ADC 466.

86 Operation Number

DLMS Note:

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.

98 Container/Packaging Specification Number
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Code Name

004010F511M5MA56 18 March 29, 2024

DLMS Note:

DLA Disposition Services uses to identify the Disposition Services Container Identification (ID). DLA

Disposition Services uses container ID on requisitions to link the DTID Number to the applicable

container. DLMS enhancement; refer to ADC 466.

9R Job Order Number

DLMS Note:

1. Use to identify, or to modify, the Job Order (JO) Number.

2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

3. For DoD SLOA/Accounting Classification compliance the JO Number may be repeated as a Work

Order Number (FA201 Qualifier WO). Refer to ADC 1043.

AN Associated Purchase Orders

DLMS Note:

1. Use for cross-reference to the customer’s internal Purchase Order (PO) Number (one PO Number

per requisition document number) or other internal reference number. When submitted, this value will

be perpetuated to subsequent transactions. Authorized for DLA interface with the Exchange, NEXCOM,

MCX, and non-DoD customers as required. (See ADC 473A and ADC 1465.

2. Use to identify the FEMA Logistics Supply Chain Management System (LSCMS) Distribution Order

Number. Refer to ADC 1306.

1. Use for cross-reference to the customer’s internal Purchase Order (PO) Number (one PO Number

per requisition document number) or other internal reference number. When submitted, this value will

be perpetuated to subsequent transactions. Authorized for DLA interface with the Exchange, NEXCOM,

MCX, and non-DoD customers as required. (See ADC 473A and ADC 1465.

2. Use to identify the FEMA Logistics Supply Chain Management System (LSCMS) Distribution Order

Number. Refer to ADC 1306.

CO Customer Order Number

DLMS Note:

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).

CT Contract Number

DLMS Note:

Use to identify the procurement instrument identifier (PIID) of the ordering instrument associated with

the FedMall/part numbered catalog order.

F8 Original Reference Number

DLMS Note:

1. Use to identify the Prior Requisition Document Number when re-requisitioning materiel subsequent to

purchase of materiel from DLA. Applicable when re-requisitioning is due to storage activity denial or

receipt of quality deficient materiel.

2. Authorized DLMS enhancement for BRAC IMSP only. Refer to ADC 352 and ADC 359.

IT Internal Customer Number

DLMS Note:

Use to identify the DoD EMALL-generated customer identification or other authorized submitter of

requisitions containing in-the-clear exception ship-to addressing.

TN Transaction Reference Number

DLMS Note:

1. Must use to identify the transaction number of the requisition. This is the document number.

2. When used in the requisition alert (BR06=83), this will be the requisition alert document number. 

The requisition alert document number is an authorized DLMS enhancement under DLA industrial

activity support agreement. Refer to ADC 381.

W4 Procurement Request Number

DLMS Note:

Use to identify a procurement request associated with the requisition when no contract number is

assigned.

W6 Federal Supply Schedule Number

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

WO Work Order Number
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Code Name

004010F511M5MA56 19 March 29, 2024

DLMS Note:

1. Use to identify a maintenance work order number.

2. DLMS enhancement; see introductory DLMS note 3a.

3. For DoD SLOA/Accounting Classification compliance the Work Order Number may be repeated at

FA201 Qualifier WO. Refer to ADC 1043.

WP Warehouse Pick Ticket Number

DLMS Note:

1. Use to identify, or to modify, the picklist control number assigned to identify a specific job for which

materiels are being requisitioned and assembled together in support of planned maintenance. 

2. Cite the picklist control number in N903 due to field length.

3. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

GTC General Terms and Conditions Identifier 

DLMS Note:

1. Use to identify the Fiscal Service (FS) Form 7600A General Terms and Conditions (GT&C) number in

G- Invoicing related transactions. Refer to ADC 1465.

2. DLMS enhancement; see introductory DLMS note 3a.

3. At this time a local code GTC is established for use in 511M version 4010. A data maintenance

action will be submitted to ASC X12 to establish GTC, General Terms and Conditions Identifier, in a

future version.

1. Use to identify the Fiscal Service (FS) Form 7600A General Terms and Conditions (GT&C) number in

G- Invoicing related transactions. Refer to ADC 1465.

2. DLMS enhancement; see introductory DLMS note 3a.

3. At this time a local code GTC is established for use in 511M version 4010. A data maintenance

action will be submitted to ASC X12 to establish GTC, General Terms and Conditions Identifier, in a

future version.

PWC Preliminary Work Candidate Number

DLMS Note:

1. Use to identify a Requisition Alert Document Number. 

2. Used by Navy Shipyards to associate the funded requisition modification with a previously submitted

requisition alert. 

3. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

N902 127 Reference Identification

Description: Reference information as defined for a

particular Transaction Set or as specified by the

Reference Identification Qualifier

X AN 1/30 Used

N903 369 Free-form Description

Description: Free-form descriptive text

X AN 1/45 Used

N907 C040 Reference Identifier

Description: To identify one or more reference

numbers or identification numbers as specified by

the Reference Qualifier

O Comp Used

N907-01 128 Reference Identification Qualifier

Description: Code qualifying the Reference

Identification

M ID 2/3 Must use

Code Name

43 Supporting Document Number

DLMS Note:

1. Use to identify the Special Program Requirement (SPR) transaction number.

2. Use with N901 code TN to identify the Special Program Requirement (SPR) transaction number and

establish an audit trail between the draw-down requisition and the original SPR against which the

requirement was established.
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Code Name

004010F511M5MA56 20 March 29, 2024

3. DLMS enhancement; see introductory DLMS note 3a.

55 Sequence Number

DLMS Note:

DLA Disposition Services uses in conjunction with the Disposition Services Container ID in N901 to

identify the Disposition Services Container DTID Sequence Number. This is a sequential number

assigned for the requisitioned DTIDs that make up a container. Only applicable if an entire container is

requisitioned. Refer to ADC 466.

C7 Contract Line Item Number

DLMS Note:

Use with N901 code CT, to identify the associated contract line item number (CLIN), including the sub

contract line item (SUBCLIN), or agreement line item number (ALIN), as appropriate.

IX Item Number

DLMS Note:

1. Use with N901 code W6 to indicate the Federal Supply Schedule Special Item Number.

2. DLMS enhancement; see introductory DLMS note 3a.

W1 Disposal Turn-In Document Number

DLMS Note:

1. Use in conjunction with the requisition document number (N901 Code TN) when requisitioning a

specific item from DLA Disposition Services.

2. When there is no Suffix Code (N907 Code W8), associated with the customer’s Document Number,

enter the correlating DTID in the N907-02. If there is a Suffix Code, then enter the DTID in the N907-04.

 DLMS enhancement, see ADC 466.

W8 Suffix

DLMS Note:

1. Use with N901 code TN to identify the document number suffix. Use when the initial 511R transaction

is identified as a referral order with BR02 transaction type code BN and is referring a quantity less than

the original requisition quantity to another supply source, with the exception of a modifications from the

supply source to a procurement activity. For these modifications, enter the suffix as shown in the

procurement request; otherwise leave blank.

2. Also authorized on an Intra-Army basis with N901 code TN for identification of the post-post partial

issue of materiel by Army Single Stock Fund activities when the initial 511R transaction BR02

transaction type code is A0 and BR06 action code is “J”.

3. Use with N901 Code F8 to identify the Prior requisition document number suffix if applicable. 

Authorized DLMS enhancement for BRAC IMSP only. Refer to ADC 352 and ADC 359.

4. When used in modification of the requisition alert (BR06=83), or when used in association with the

Requisition Alert Document Number (Qualifier PWC, above), this will be the requisition alert document

suffix. Use with BR02 Qualifier BN only. The requisition alert document number suffix is an authorized

DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

5. DLA Disposition Services uses on an intra-DLA basis for requisitions processed between the RTD

Web Application and DLA Disposition Services. The RTD Web-sequentially assigned suffix code is

used for open requisition quantity on externally submitted requisitions when required to establish

separate requisition transactions to DLA Disposition Services by DTID Number and, when applicable,

the associated DTID Suffix Code. Refer to ADC 466.

1. Use with N901 code TN to identify the document number suffix. Use when the initial 511R transaction

is identified as a referral order with BR02 transaction type code BN and is referring a quantity less than

the original requisition quantity to another supply source, with the exception of a modifications from the

supply source to a procurement activity. For these modifications, enter the suffix as shown in the

procurement request; otherwise leave blank.

2. Also authorized on an Intra-Army basis with N901 code TN for identification of the post-post partial

issue of materiel by Army Single Stock Fund activities when the initial 511R transaction BR02

transaction type code is A0 and BR06 action code is “J”.

3. Use with N901 Code F8 to identify the Prior requisition document number suffix if applicable. 

Authorized DLMS enhancement for BRAC IMSP only. Refer to ADC 352 and ADC 359.

4. When used in modification of the requisition alert (BR06=83), or when used in association with the

Requisition Alert Document Number (Qualifier PWC, above), this will be the requisition alert document

suffix. Use with BR02 Qualifier BN only. The requisition alert document number suffix is an authorized

DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

5. DLA Disposition Services uses on an intra-DLA basis for requisitions processed between the RTD

Web Application and DLA Disposition Services. The RTD Web-sequentially assigned suffix code is

used for open requisition quantity on externally submitted requisitions when required to establish

separate requisition transactions to DLA Disposition Services by DTID Number and, when applicable,

the associated DTID Suffix Code. Refer to ADC 466.

N907-02 127 Reference Identification

Description: Reference information as defined for a

particular Transaction Set or as specified by the

Reference Identification Qualifier

M AN 1/30 Must use

N907-03 128 Reference Identification Qualifier

Description: Code qualifying the Reference

Identification

X ID 2/3 Used
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 21 March 29, 2024

Code Name

W1 Disposal Turn-In Document Number

DLMS Note:

1. Use in conjunction with the requisition document number (N901 Code TN) when requisitioning a

specific item from DLA Disposition Services.

 2. When there is no Suffix Code associated with the customer’s Document Number, enter the

correlating DTID in the N907-02. If there is a Suffix Code, then enter the DTID in the N907-04. DLMS

enhancement, see ADC 466.

1. Use in conjunction with the requisition document number (N901 Code TN) when requisitioning a

specific item from DLA Disposition Services.

 2. When there is no Suffix Code associated with the customer’s Document Number, enter the

correlating DTID in the N907-02. If there is a Suffix Code, then enter the DTID in the N907-04. DLMS

enhancement, see ADC 466.

N907-04 127 Reference Identification

Description: Reference information as defined for a

particular Transaction Set or as specified by the

Reference Identification Qualifier

X AN 1/30 Used

N907-05 128 Reference Identification Qualifier

Description: Code qualifying the Reference

Identification

X ID 2/3 Used

N907-06 127 Reference Identification

Description: Reference information as defined for a

particular Transaction Set or as specified by the

Reference Identification Qualifier

X AN 1/30 Used
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 22 March 29, 2024

PO1 Baseline Item Data Pos: 30 Max: >1

Detail - Optional

Loop: LX Elements: 14

User Option (Usage): Used

Purpose: To specify basic and most frequently used line item data

Syntax Rules: 

1. C0302 - If PO103 is present, then PO102 is required.

2. C0504 - If PO105 is present, then PO104 is required.

3. P0607 - If either PO106 or PO107 is present, then the other is required.

4. P0809 - If either PO108 or PO109 is present, then the other is required.

5. P1011 - If either PO110 or PO111 is present, then the other is required.

6. P1213 - If either PO112 or PO113 is present, then the other is required.

7. P1415 - If either PO114 or PO115 is present, then the other is required.

8. P1617 - If either PO116 or PO117 is present, then the other is required.

9. P1819 - If either PO118 or PO119 is present, then the other is required.

10. P2021 - If either PO120 or PO121 is present, then the other is required.

11. P2223 - If either PO122 or PO123 is present, then the other is required.

12. P2425 - If either PO124 or PO125 is present, then the other is required.

Comments: 

1. See the Data Element Dictionary for a complete list of IDs.

2. PO101 is the line item identification.

3. PO106 through PO125 provide for ten different product/service IDs per each item. For example: Case, Color, Drawing No., U.P.C. No.,

ISBN No., Model No., or SKU.

DLMS Note:

Must use this 2/PO1/030 segment to identify the materiel and other information required to process the modification as a requisition.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

PO102 330 Quantity Ordered

Description: Quantity ordered

DLMS Note: 1. Must use to identify the

requisitioned quantity.

2. Express as a whole number with no decimal.

3. A field size exceeding 5 positions (7 positions for

FSG 13, ammunition) may not be received or

understood by the recipient's automated processing

system. See introductory DLMS note 3d.

X R 1/15 Must use

PO103 355 Unit or Basis for Measurement Code

Description: Code specifying the units in which a

value is being expressed, or manner in which a

measurement has been taken

DLMS Note: 1. Use to identify the unit of issue for

the materiel requisitioned.

2. DLMS users see the DLMS Unit of Issue and

Purchase Unit Conversion Table for available codes.

O ID 2/2 Used

PO104 212 Unit Price

Description: Price per unit of product, service,

commodity, etc.

DLMS Note: 1. For nonreimbursable materiel (free

X R 1/17 Used
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004010F511M5MA56 23 March 29, 2024

issue), indicate 0 dollars. Use with P0105 Code NC,

No Charge. DLMS migration enhancement. This

usage is comparable to Signal Code D or M.

2. Use for nonstandard materiel to indicate an

estimated price. Estimated unit price for

nonstandard materiel is a DLMS enhancement, see

introductory DLMS note 3a.

3. For intra-Air Force, the unit price will be

perpetuated to the requisition modifier.

4. DLMS transactions authorize an expanded unit

price field size of 9 digits for dollars and 2 digits for

cents. The decimal point is passed in the

transaction. If conversion to MILS legacy format is

required, unit prices exceeding the legacy field size

constraint will not be perpetuated. Authorized

DLMS migration enhancement. Refer to ADC 221A.

4. DLMS transactions authorize an expanded unit

price field size of 9 digits for dollars and 2 digits for

cents. The decimal point is passed in the

transaction. If conversion to MILS legacy format is

required, unit prices exceeding the legacy field size

constraint will not be perpetuated. Authorized

DLMS migration enhancement. Refer to ADC 221A.

PO105 639 Basis of Unit Price Code

Description: Code identifying the type of unit price

for an item

DLMS Note: Use for nonstandard and

nonreimbursable (free issue) materiel. For

nonstandard materiel, use to identify an estimated

unit price.

O ID 2/2 Used

Code Name

ES Estimated

DLMS Note:

Use to indicate an estimated unit price for the nonstandard materiel.

NC No Charge

DLMS Note:

Use to indicate nonreimbursable (free issue) materiel. DLMS migration enhancement. This usage is

comparable to Signal Code D or M.

UM Price per Unit of Measure

DLMS Note:

Use for intra-Air Force.

PO106 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

DLMS Note: 1. Use only one of codes A2, A4, FB,

FS, FT, MG, SW, YP or ZZ to identify the materiel

requisitioned. Must use the National Stock Number

(NSN) (code FS) when known, except when

appropriate for brand name subsistence items

identified by a Subsistence Identification Number.

DLMS Note: 1. Use only one of codes A2, A4, FB,

FS, FT, MG, SW, YP or ZZ to identify the materiel

requisitioned. Must use the National Stock Number

(NSN) (code FS) when known, except when

appropriate for brand name subsistence items

identified by a Subsistence Identification Number.

2. The following codes are authorized.

X ID 2/2 Must use

Code Name

A2 Department of Defense Identification Code (DoDIC)

DLMS Note:

1. Use to identify ammunition items.

2. DLMS enhancement; see introductory DLMS note 3a.

A4 Subsistence Identification Number

DLMS Note:

Use to identify subsistence items.
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Code Name

004010F511M5MA56 24 March 29, 2024

FB Form Number

DLMS Note:

1. Use to identify the form stock number.

2. DLMS enhancement; see introductory DLMS note 3a.

FS National Stock Number

DLMS Note:

1. Use to identify the NSN. 

2. When the unit of use indicator is included (1/BR01/20=ZZ), the NSN ordered will be interpreted as a

unit of use requirement so that the order may be processed against the associated DLA-assigned LSN.

The requested quantity is expressed in the unit of use for the LSN in lieu of the unit of issue for the

identified NSN. Authorized DLMS enhancement under DLA industrial activity support agreement.

FT Federal Supply Classification

DLMS Note:

Use to identify the FSC of the nonstandard materiel when a part number is not available and materiel

can only be ordered by description (e.g., non-NSN lumber products).

MG Manufacturer's Part Number

DLMS Note:

1. Use to identify nonstandard materiel.

2. May be used to identify the supplier-assigned part number when applicable to a DoD EMALL or GSA

Advantage/Global internet order from a vendor catalog. Refer to ADC 1068.

SW Stock Number

DLMS Note:

1. Use to identify the local stock number (LSN).

2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

YP Publication Number

DLMS Note:

1. Use to identify the publication stock number.

2. DLMS enhancement; see introductory DLMS note 3a.

ZZ Mutually Defined

DLMS Note:

Use to identify nonstandard materiel when all other authorized codes do not apply (includes

management control numbers and locally assigned control numbers). May be used for legacy

MILSTRIP-to-DLMS conversion when the translator cannot determine a more appropriate code.

PO107 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Must use

PO108 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

DLMS Note: 1. Use only one of codes CN or ZB to

fully identify the materiel.

2. Use PO110 and PO111 when both one of CN or

ZB and JP is needed.

X ID 2/2 Used

Code Name

CN Commodity Name

DLMS Note:

1. Use with PO106 code FT to identify the materiel name or description.

2. Use to identify the FEMA Logistics Supply Chain Management System (LSCMS) Item Name. Refer 
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Code Name

004010F511M5MA56 25 March 29, 2024

to ADC 1306.

JP Package Type Code

DLMS Note:

Must use to indicate Outside Continental United States (OCONUS) shipment. When used, the paired

data element 234 will cite 1 indicating that packaging must meet OCONUS specifications.

ZB Commercial and Government Entity (CAGE) Code

DLMS Note:

1. Use only with 2/PO1/030 PO106 code MG to uniquely identify a manufacturer's (or supplier’s) part

number.

2. May be used to identify the supplier CAGE when applicable to a DoD EMALL or GSA

Advantage/Global internet order from a vendor catalog.

PO109 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

PO110 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

X ID 2/2 Used

PO111 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

PO112 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

DLMS Note: The following codes are authorized.

X ID 2/2 Used

Code Name

A3 Locally Assigned Control Number

DLMS Note:

1. Defense Medical Logistics Standard Support (DMLSS)/Theater Enterprise-Wide Logistics System

(TEWLS) use to cite their Local Catalog Identification for subsequent use as the stock number

applicable to receipt and inventory processing. Must be used with the manufacturer’s part number and

associated CAGE cited above.

2. DLMS enhancement; see introductory DLMS Note 3a. Refer to ADC 322.

3. Under DLMS, field length is restricted to a maximum of 30 positions.

1. Defense Medical Logistics Standard Support (DMLSS)/Theater Enterprise-Wide Logistics System

(TEWLS) use to cite their Local Catalog Identification for subsequent use as the stock number

applicable to receipt and inventory processing. Must be used with the manufacturer’s part number and

associated CAGE cited above.

2. DLMS enhancement; see introductory DLMS Note 3a. Refer to ADC 322.

3. Under DLMS, field length is restricted to a maximum of 30 positions.

PO113 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

PO114 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

DLMS Note: Use only one of codes EN, UK, or UP

to identify items by Global Trade Item Number.

DLMS enhancements. Authorized for use by

non-DoD customers. Refer to ADC 1307 and ADC

1307A.

DLMS Note: Use only one of codes EN, UK, or UP

to identify items by Global Trade Item Number.

DLMS enhancements. Authorized for use by

non-DoD customers. Refer to ADC 1307 and ADC

1307A.

X ID 2/2 Used

Code Name

EN European Article Number (EAN) (2-5-5-1)

DLMS Note:
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Code Name

004010F511M5MA56 26 March 29, 2024

1. This is the Global Trade Item Number (GTIN)-13.

2. DLMS enhancement. See introductory DLMS note 3a.

UK U.P.C./EAN Shipping Container Code (1-2-5-5-1)

DLMS Note:

1. This is the Global Trade Item Number (GTIN)-14

2. DLMS enhancement. See introductory DLMS note 3a.

UP U.P.C. Consumer Package Code (1-5-5-1)

DLMS Note:

1. This Global Trade Item Number (GTIN)-12.

2. DLMS enhancement. See introductory DLMS note 3a.

PO115 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 27 March 29, 2024

DD Demand Detail Pos: 60 Max: 100

Detail - Optional

Loop: LX Elements: 9

User Option (Usage): Used

Purpose: To describe the type of demand and the intended use of material

Syntax Rules: 

1. C0201 - If DD02 is present, then DD01 is required.

2. P030405 - If either DD03, DD04 or DD05 are present, then the others are required.

3. C0605 - If DD06 is present, then DD05 is required.

4. C1009 - If DD10 is present, then DD09 is required.

Semantics: 

1. DD08 transmits the stock level indicator. A "Y" indicates that the material is normally carried in stock; an "N" indicates that the material

is not normally stocked.

DLMS Note:

1. As an option, use multiple repetitions to stratify the quantity requisitioned by weapon system and associated demand code. The total

quantity identified in all repetitions must equal the quantity in PO102.

2. Use to convey the demand code associated with the requisition and, as appropriate, to identify the applicable weapon system for which

the item is being requisitioned.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

DD01 1271 Industry Code

Description: Code indicating a code from a specific

industry code list

X AN 1/30 Must use

DD02 1270 Code List Qualifier Code

Description: Code identifying a specific industry

code list

O ID 1/3 Must use

Code Name

74 Demand Code

DLMS Note:

1. Must use to identify, or to modify, the applicable Demand Code indicating whether the demand is

recurring or nonrecurring.

2. Demand code added to the Referral Order (A4_) format by Approved MILSTRIP Change 44.

3. Stratification of quantity by demand code is a potential future DLMS enhancement; see introductory

DLMS note 3a.

DD03 128 Reference Identification Qualifier

Description: Code qualifying the Reference

Identification

X ID 2/3 Used

Code Name

W2 Weapon System Number

DLMS Note:

1. Use to identify the applicable weapon system designator code.

2. DLMS enhancement; see introductory DLMS note 3a.

DD04 127 Reference Identification X AN 1/30 Used
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004010F511M5MA56 28 March 29, 2024

Description: Reference information as defined for a

particular Transaction Set or as specified by the

Reference Identification Qualifier

DD05 1271 Industry Code

Description: Code indicating a code from a specific

industry code list

DLMS Note: Use to identify the Service associated

with the weapon system for which this demand is

reported.

X AN 1/30 Used

DD06 1270 Code List Qualifier Code

Description: Code identifying a specific industry

code list

O ID 1/3 Used

Code Name

71 Service and Agency Code

DLMS Note:

1. Use to identify the Service/Agency code associated with the stratified demand data.

2. DLMS enhancement; see introductory DLMS note 3a.

DD07 380 Quantity

Description: Numeric value of quantity

DLMS Note: Use to identify the quantity associated

with the weapon system and associated demand

code.

O R 1/15 Used

DD09 1271 Industry Code

Description: Code indicating a code from a specific

industry code list

X AN 1/30 Used

DD10 1270 Code List Qualifier Code

Description: Code identifying a specific industry

code list

O ID 1/3 Used

Code Name

98 Reason for Requisitioning Code

DLMS Note:

1. Use to identify, or to modify, the Reason for Requisitioning Code. Used by Naval IAs specifying use

of the materiel requirement.

2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 29 March 29, 2024

GF Furnished Goods and Services Pos: 70 Max: 1

Detail - Optional

Loop: LX Elements: 6

User Option (Usage): Used

Purpose: To specify information related to furnished material, equipment, property, information, and services

Syntax Rules: 

1. P0102 - If either GF01 or GF02 is present, then the other is required.

2. P0506 - If either GF05 or GF06 is present, then the other is required.

3. P0809 - If either GF08 or GF09 is present, then the other is required.

Semantics: 

1. GF04 is the value of government-furnished property.

DLMS Note:

1. Use in all Government Furnished Materiel (GFM) related transactions.

2. Must use to provide contract information applicable to the procurement source under which the contractor is authorized to receive GFP. 

3. May be used provide contract information applicable to the procurement source under which the contractor is authorized to purchase from

a Government source when directed by the authorizing Service/Agency under CFM procedures.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

GF01 128 Reference Identification Qualifier

Description: Code qualifying the Reference

Identification

X ID 2/3 Used

Code Name

C7 Contract Line Item Number

DLMS Note:

1. Use to associate a Contract Line Item Number with the PIID.

2. Use in CAV transactions or as directed by the authorizing Service/Agency.

3. When both the CLIN and the MDN are applicable, identify the CLIN in GF09. Refer to ADC 1014A.

W3 Manufacturing Directive Number

DLMS Note:

1. Use to associate a Contract Line Item Number with the PIID.

2. Use as directed by the authorizing Service/Agency. Refer to ADC 1014.

3. When both the CLIN and the MDN are applicable, identify the CLIN in GF09. Refer to ADC 1014A.

GF02 127 Reference Identification

Description: Reference information as defined for a

particular Transaction Set or as specified by the

Reference Identification Qualifier

X AN 1/30 Used

GF03 367 Contract Number

Description: Contract number

DLMS Note: 1. Must use to identify the PIID for 

GFM. Refer to ADC 1161A.

2. Use as directed by the authorizing

Service/Agency to identify the PIID authorizing the

contractor to purchase materiel from a Government 

O AN 1/30 Used
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004010F511M5MA56 30 March 29, 2024

source. Use the legacy procurement instrument

identification number (PIIN) pending transition to the

PIID. When GFM is authorized under a PIID

call/order number (F in 9th position), provide the

value in the PIID field. For Other Transaction (OT)

agreements, the type of instrument (9th position of

PIID) will be 3 for Research OTs or 9 for Prototype

and Production OTs. Refer to ADC 1420.

source. Use the legacy procurement instrument

identification number (PIIN) pending transition to the

PIID. When GFM is authorized under a PIID

call/order number (F in 9th position), provide the

value in the PIID field. For Other Transaction (OT)

agreements, the type of instrument (9th position of

PIID) will be 3 for Research OTs or 9 for Prototype

and Production OTs. Refer to ADC 1420.

3. Fully compliant DLMS applications must support

identification of the thirteen-position PIID, rather

than the abridged contract number authorized for

legacy MILSTRIP. Refer to ADC 1014.

GF07 328 Release Number

Description: Number identifying a release against a

Purchase Order previously placed by the parties

involved in the transaction

DLMS Note: 1. Use to identify the legacy

four-position call/order number associated with the

legacy PIIN. 

2. Do not use for the PIID call/order number. The

PIID call/order number is mapped to GF03. Refer to

ADC 1161A.

3. Use as directed by the authorizing

Service/Agency.

O AN 1/30 Used

GF08 128 Reference Identification Qualifier

Description: Code qualifying the Reference

Identification

X ID 2/3 Used

Code Name

C7 Contract Line Item Number

DLMS Note:

1. Use to associate a Contract Line Item Number with the Contract Number when also identifying an

MDN (at GF01).

2. Use as directed by the authorizing Service/Agency. Refer to ADC 1014A. 

GF09 127 Reference Identification

Description: Reference information as defined for a

particular Transaction Set or as specified by the

Reference Identification Qualifier

X AN 1/30 Used
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 31 March 29, 2024

G62 Date/Time Pos: 80 Max: 20

Detail - Optional

Loop: LX Elements: 2

User Option (Usage): Used

Purpose: To specify pertinent dates and times

Syntax Rules: 

1. R0103 - At least one of G6201 or G6203 is required.

2. P0102 - If either G6201 or G6202 is present, then the other is required.

3. P0304 - If either G6203 or G6204 is present, then the other is required.

DLMS Note:

Use multiple repetitions to identify unique dates or delivery periods associated with the requisitioner's requirements.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

G6201 432 Date Qualifier

Description: Code specifying type of date

X ID 2/2 Must use

Code Name

53 Deliver Not Before Date

DLMS Note:

Use to modify, or in the case of an unmatched modification, to identify the earliest acceptable delivery

date for the materiel requisitioned. For conventional ammunition requirements, it defines the earliest

acceptable delivery date for the required delivery period.

54 Deliver No Later Than Date

DLMS Note:

Use to modify, or in the case of an unmatched modification, to identify the latest acceptable delivery

date for the materiel requisitioned. For conventional ammunition requirements, it defines the latest

acceptable delivery date for the required delivery period.

68 Requested Delivery Date

DLMS Note:

For DLA use only to identify the DLA-calculated delivery date used for internal processing of a

customer order.

85 Date Issued

DLMS Note:

1, This is the date a drawing or drawing revision was issued.

2. Use only when requisitioning nonstandard materiel. Cite the effective date of the drawing number

(when only using code PT) or the drawing revision number (when using code DR with code PT)

identified in the 2/LIN/100 segment.

3. DLMS enhancement.

BC Publication Date

DLMS Note:

Use only when requisitioning nonstandard materiel to cite the manufacturer's catalog publication date

when a catalog is identified in the 2/LIN/100 segment.

BD Required By

DLMS Note:

For FMS and MAP/GA requirements, use to modify, or in the case of an unmatched modification, to

identify the required availability date. For all other uses, it is the revised or required delivery date.

G6202 373 Date

Description: Date expressed as CCYYMMDD

X DT 8/8 Must use
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004010F511M5MA56 32 March 29, 2024
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 33 March 29, 2024

LIN Item Identification Pos: 100 Max: >1

Detail - Optional

Loop: LX Elements: 30

User Option (Usage): Used

Purpose: To specify basic item identification data

Syntax Rules: 

1. P0405 - If either LIN04 or LIN05 is present, then the other is required.

2. P0607 - If either LIN06 or LIN07 is present, then the other is required.

3. P0809 - If either LIN08 or LIN09 is present, then the other is required.

4. P1011 - If either LIN10 or LIN11 is present, then the other is required.

5. P1213 - If either LIN12 or LIN13 is present, then the other is required.

6. P1415 - If either LIN14 or LIN15 is present, then the other is required.

7. P1617 - If either LIN16 or LIN17 is present, then the other is required.

8. P1819 - If either LIN18 or LIN19 is present, then the other is required.

9. P2021 - If either LIN20 or LIN21 is present, then the other is required.

10. P2223 - If either LIN22 or LIN23 is present, then the other is required.

11. P2425 - If either LIN24 or LIN25 is present, then the other is required.

12. P2627 - If either LIN26 or LIN27 is present, then the other is required.

13. P2829 - If either LIN28 or LIN29 is present, then the other is required.

14. P3031 - If either LIN30 or LIN31 is present, then the other is required.

Semantics: 

1. LIN01 is the line item identification

Comments: 

1. See the Data Dictionary for a complete list of IDs.

2. LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No.,

ISBN No., Model No., or SKU.

DLMS Note:

1. Use to provide a detailed description of the nonstandard materiel identified in PO106 with code FT or MG. Use with the MEA, G62

(2/LX/010 loop, position 080), N1 (2/N1/180 loop), and G69 segments to fully identify the nonstandard materiel.

2. Use data element 235/234 pairs to identify data pertinent to the transaction. Present the information in any sequential order. Unless

otherwise specified, the multiple codes listed for a single qualifier data element identify the range of possible data requirements. When

needed, use the next available combination of data element 235/234 pairs to provide the necessary data.

3. Must use when requisitioning nonstandard materiel.

1. Use to provide a detailed description of the nonstandard materiel identified in PO106 with code FT or MG. Use with the MEA, G62

(2/LX/010 loop, position 080), N1 (2/N1/180 loop), and G69 segments to fully identify the nonstandard materiel.

2. Use data element 235/234 pairs to identify data pertinent to the transaction. Present the information in any sequential order. Unless

otherwise specified, the multiple codes listed for a single qualifier data element identify the range of possible data requirements. When

needed, use the next available combination of data element 235/234 pairs to provide the necessary data.

3. Must use when requisitioning nonstandard materiel.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

LIN02 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

DLMS Note: The following codes are authorized.

M ID 2/2 Must use

Code Name

AB Assembly

DLMS Note:

Use to identify the assembly associated with the materiel.

BH Finish/Hand Standard Reference

DLMS Note:

Use to identify the fabric of the nonstandard materiel ordered under Federal Supply Schedule.
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Code Name

004010F511M5MA56 34 March 29, 2024

CL Color

CN Commodity Name

DLMS Note:

1. Use to identify the nomenclature of the non-NSN materiel.

2. During the legacy MILSTRIP/DLMS transition, this field will be used to perpetuate/populate the Noun

Description of Item on MILSTRIP part-numbered requisition (corresponds to A02/A0B with Identification

Code C (rp 70)). During this time, a field length greater than 10 positions may be truncated or dropped

by the receiving application. 

3. Under full DLMS, the field length shall be expanded to conform to this standard which allows 48

positions. DLMS-capable applications should plan to support this expanded field length as a DLMS

enhancement. See introductory DLMS 3f.

1. Use to identify the nomenclature of the non-NSN materiel.

2. During the legacy MILSTRIP/DLMS transition, this field will be used to perpetuate/populate the Noun

Description of Item on MILSTRIP part-numbered requisition (corresponds to A02/A0B with Identification

Code C (rp 70)). During this time, a field length greater than 10 positions may be truncated or dropped

by the receiving application. 

3. Under full DLMS, the field length shall be expanded to conform to this standard which allows 48

positions. DLMS-capable applications should plan to support this expanded field length as a DLMS

enhancement. See introductory DLMS 3f.

CR Contract Number

DLMS Note:

Use to identify the PIID of the Federal Supply Schedule or related instrument when ordering

nonstandard materiel. When procurement is authorized under a PIID call/order number (F in 9th

position), provide the value in the PIID field. For Other Transaction (OT) agreements, the type of

instrument (9th position of PIID) will be 3 for Research OTs or 9 for Prototype and Production OTs. 

Refer to ADC 1161A or ADC 1420.

DR Drawing Revision Number

F1 Catalog Number

DLMS Note:

Use to identify the manufacturer's catalog which references the nonstandard materiel. Cite the effective

catalog publication date, if applicable, in the 2/G62/080 segment.

F2 Technical Order Number

DLMS Note:

1. During the legacy MILSTRIP/DLMS transition, this field will be used to perpetuate/populate the

Technical Order Number/Technical Manual Number identified on MILSTRIP part-numbered requisition

(corresponds to AM2/AMB with Identification Code A (rp 70). During this time, a field length greater

than 10 positions may be truncated or dropped by the receiving application. 

2. Under full DLMS, the field length shall be expanded to conform to this standard which allows 48

positions. DLMS-capable applications should plan to support this expanded field length as a DLMS

enhancement. See introductory DLMS 3f.

1. During the legacy MILSTRIP/DLMS transition, this field will be used to perpetuate/populate the

Technical Order Number/Technical Manual Number identified on MILSTRIP part-numbered requisition

(corresponds to AM2/AMB with Identification Code A (rp 70). During this time, a field length greater

than 10 positions may be truncated or dropped by the receiving application. 

2. Under full DLMS, the field length shall be expanded to conform to this standard which allows 48

positions. DLMS-capable applications should plan to support this expanded field length as a DLMS

enhancement. See introductory DLMS 3f.

F3 Technical Manual Number

F4 Series Identifier

DLMS Note:

Use to identify the manufacturer's series number of the end item.

F7 End-Item Description

DLMS Note:

1. Use to identify the applicable end item which applies to the non-NSN materiel. Description may

include the NSN of the end item and/or nomenclature.

2. During the legacy MILSTRIP/DLMS transition, this field will be used to perpetuate/populate the End

Item Identification on MILSTRIP part-numbered requisition (corresponds to A02/A0B with Identification

Code B (rp 70)). During this time, a field length greater than 10 positions may be truncated or dropped

by the receiving application. 

3. Under full DLMS, the field length shall be expanded to conform to this standard which allows 48

positions. DLMS-capable applications should plan to support this expanded field length as a DLMS

enhancement. See introductory DLMS 3f.

1. Use to identify the applicable end item which applies to the non-NSN materiel. Description may

include the NSN of the end item and/or nomenclature.

2. During the legacy MILSTRIP/DLMS transition, this field will be used to perpetuate/populate the End

Item Identification on MILSTRIP part-numbered requisition (corresponds to A02/A0B with Identification

Code B (rp 70)). During this time, a field length greater than 10 positions may be truncated or dropped

by the receiving application. 

3. Under full DLMS, the field length shall be expanded to conform to this standard which allows 48

positions. DLMS-capable applications should plan to support this expanded field length as a DLMS

enhancement. See introductory DLMS 3f.

GS General Specification Number

DLMS Note:

Use to identify a specification number, other than a Military Specification (MILSPEC), associated with

the nonstandard materiel.

MF Manufacturer

DLMS Note:
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Code Name

004010F511M5MA56 35 March 29, 2024

Use to identify the manufacturer's make of the applicable end item for the nonstandard materiel.

MN Model Number

DLMS Note:

Use to identify the manufacturer's model number of the end item.

MS Military Specification (MILSPEC) Number

PR Process Number

DLMS Note:

Use to identify a general operating specification which cannot be identified by use of the 2/MEA/105

segment. For example, the MEA use is primarily to identify physical sizes and dimensions of

nonstandard materiel. Code PR use is to indicate specifications similar to output rated wattage and

horsepower.

PT Print or Drawing

DLMS Note:

1. Use to identify the applicable drawing numbers for the nonstandard materiel.

2. During the legacy MILSTRIP/DLMS transition, this field will be used to perpetuate/populate the

Drawing or Specification Number on MILSTRIP part-numbered requisition (corresponds to A02/A0B

with Identification Code D (rp 70)). During this time, a field length greater than 10 positions may be

truncated or dropped by the receiving application. 

3. Under full DLMS, the field length shall be expanded to conform to this standard which allows 48

positions. DLMS-capable applications should plan to support this expanded field length as a DLMS

enhancement. See introductory DLMS 3f.

1. Use to identify the applicable drawing numbers for the nonstandard materiel.

2. During the legacy MILSTRIP/DLMS transition, this field will be used to perpetuate/populate the

Drawing or Specification Number on MILSTRIP part-numbered requisition (corresponds to A02/A0B

with Identification Code D (rp 70)). During this time, a field length greater than 10 positions may be

truncated or dropped by the receiving application. 

3. Under full DLMS, the field length shall be expanded to conform to this standard which allows 48

positions. DLMS-capable applications should plan to support this expanded field length as a DLMS

enhancement. See introductory DLMS 3f.

PW Part Drawing

DLMS Note:

Use to identify the applicable figure numbers for the nonstandard materiel.

SF Surface Finish

DLMS Note:

Use to identify the finish of the nonstandard materiel ordered under Federal Supply Schedule.

SN Serial Number

DLMS Note:

Use to identify the manufacturer's serial number of the end item.

VN Vendor's (Seller's) Item Number

YP Publication Number

DLMS Note:

Use to identify publications or catalogs.

ZZ Mutually Defined

DLMS Note:

Use to identify nonstandard materiel when all other authorized codes do not apply or cannot be

determined.

LIN03 234 Product/Service ID

Description: Identifying number for a product or

service

M AN 1/48 Must use

LIN04 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

X ID 2/2 Used

LIN05 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

LIN06 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

X ID 2/2 Used
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004010F511M5MA56 36 March 29, 2024

descriptive number used in Product/Service ID (234)

LIN07 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

LIN08 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

X ID 2/2 Used

LIN09 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

LIN10 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

X ID 2/2 Used

LIN11 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

LIN12 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

X ID 2/2 Used

LIN13 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

LIN14 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

X ID 2/2 Used

LIN15 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

LIN16 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

X ID 2/2 Used

LIN17 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

LIN18 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

X ID 2/2 Used

LIN19 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

LIN20 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

X ID 2/2 Used
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004010F511M5MA56 37 March 29, 2024

LIN21 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

LIN22 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

X ID 2/2 Used

LIN23 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

LIN24 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

X ID 2/2 Used

LIN25 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

LIN26 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

X ID 2/2 Used

LIN27 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

LIN28 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

X ID 2/2 Used

LIN29 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

LIN30 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

X ID 2/2 Used

LIN31 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 38 March 29, 2024

MEA Measurements Pos: 105 Max: >1

Detail - Optional

Loop: LX Elements: 3

User Option (Usage): Used

Purpose: To specify physical measurements or counts, including dimensions, tolerances, variances, and weights(See Figures Appendix for

example of use of C001)

Syntax Rules: 

1. R03050608 - At least one of MEA03, MEA05, MEA06 or MEA08 is required.

2. C0504 - If MEA05 is present, then MEA04 is required.

3. C0604 - If MEA06 is present, then MEA04 is required.

4. L07030506 - If MEA07 is present, then at least one of MEA03, MEA05 or MEA06 is required.

5. E0803 - Only one of MEA08 or MEA03 may be present.

Semantics: 

1. MEA04 defines the unit of measure for MEA03, MEA05, and MEA06.

Comments: 

1. When citing dimensional tolerances, any measurement requiring a sign (+ or -), or any measurement where a positive (+) value cannot

be assumed, use MEA05 as the negative (-) value and MEA06 as the positive (+) value.

DLMS Note:

Use multiple repetitions to identify any measurements/dimensions related to the nonstandard materiel.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

MEA02 738 Measurement Qualifier

Description: Code identifying a specific product or

process characteristic to which a measurement

applies

DLMS Note: 1. Use to identify the specific

dimension/measurement quantified in MEA03 and

MEA04.

2. The following codes are authorized.

O ID 1/3 Used

Code Name

DI Diameter

DN Density

DP Depth

FQ Frequency

GL Gloss

HT Height

ID Inside Diameter

LN Length

MD Measurement Voltage

OD Outside Diameter

PB Pressure

TF Tensile

TH Thickness

VO Voltage

WD Width

WT Weight

LPR Line Pressure
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Code Name

004010F511M5MA56 39 March 29, 2024

UCB Cube

VOL Volume

MEA03 739 Measurement Value

Description: The value of the measurement

X R 1/20 Must use

MEA04 C001 Composite Unit of Measure

Description: To identify a composite unit of

measure(See Figures Appendix for examples of

use)

DLMS Note: Use to identify the value of the units

expressed in MEA03. For example, if the height of

the nonstandard materiel was six feet, cite 6 in

MEA03 and FT in MEA04.

X Comp Used

MEA04-01 355 Unit or Basis for Measurement Code

Description: Code specifying the units in which a

value is being expressed, or manner in which a

measurement has been taken

DLMS Note: The following codes are authorized.

M ID 2/2 Must use

Code Name

2G Volts (Alternating Current)

2H Volts (Direct Current)

2I British Thermal Units (BTUs) Per Hour

2N Decibels

70 Volt

82 Ohm

AD Bytes

AZ British Thermal Units (BTUs) per Pound

B0 British Thermal Units (BTUs) per Cubic Foot

B7 Cycles

CI Cubic Inches

CM Centimeter

CR Cubic Meter

CY Cubic Yard

FT Foot

GA Gallon

HJ Horsepower

IN Inch

KG Kilogram

LB Pound

LT Liter

MR Meter

OZ Ounce - Av

P1 Percent

P2 Pounds per Foot

PT Pint

QT Quart

R4 Calorie

SF Square Foot

SM Square Meter

SY Square Yard

TG Gross Ton
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Code Name

004010F511M5MA56 40 March 29, 2024

TN Net Ton (2,000 LB).

VA Volt-ampere per Kilogram

WA Watts per Kilogram

YD Yard
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 41 March 29, 2024

G69 Line Item Detail - Description Pos: 110 Max: >1

Detail - Optional

Loop: LX Elements: 1

User Option (Usage): Used

Purpose: To describe an item in free-form format

DLMS Note:

Use to describe nonstandard materiel identified in PO106 only with code FT or MG when the 2/LIN/100 and 2/MEA/105 segments do not

provide adequate descriptive capability. Use multiple repetitions to provide the narrative descriptive information.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

G6901 369 Free-form Description

Description: Free-form descriptive text

M AN 1/45 Must use
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 42 March 29, 2024

NTE Note/Special Instruction Pos: 120 Max: >1

Detail - Optional

Loop: LX Elements: 2

User Option (Usage): Used

Purpose: To transmit information in a free-form format, if necessary, for comment or special instruction

Comments: 

1. The NTE segment permits free-form information/data which, under ANSI X12 standard implementations, is not machine processable.

The use of the NTE segment should therefore be avoided, if at all possible, in an automated environment.

DLMS Note:

1. Use to identify exception data associated with the transaction. Use during extraordinary situations requiring manual intervention in the

requisition processing routine.

2. Exception data associated with the requisition is a DLMS enhancement; see introductory DLMS note 3a. 

3. Use with Requisition Exception Data Transaction (DLA DIC YRZ) to indicate technical/descriptive exception information or pick,

pack/special delivery instructions or extended part number. See introductory DLMS note 3f.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

NTE01 363 Note Reference Code

Description: Code identifying the functional area or

purpose for which the note applies

O ID 3/3 Used

Code Name

ORI Order Instructions

DLMS Note:

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. See introductory DLMS note 3f.

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. See introductory DLMS note 3f.

PDS Product Specification

DLMS Note:

Use with Requisition Exception Data Transaction (DLA DIC YRZ-Transaction Code PN) to indicate an

extended part number. Only a single instance of the segment is used with this NTE01 qualifier. A

maximum of 60 positions of text (including spaces) may be sent. See introductory DLMS note 3f.

NTE02 352 Description

Description: A free-form description to clarify the

related data elements and their content

DLMS Note: The field size is limited to a maximum

of 60 positions (including spaces) in each

occurrence of NTE02. The total positions allowed is

limited to 1200 (including spaces) which is a

maximum of 20 occurrences of the NTE02. See

introductory DLMS note 3d.

DLMS Note: The field size is limited to a maximum

of 60 positions (including spaces) in each

occurrence of NTE02. The total positions allowed is

limited to 1200 (including spaces) which is a

maximum of 20 occurrences of the NTE02. See

introductory DLMS note 3d.

M AN 1/80 Must use
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 43 March 29, 2024

LM Code Source Information Pos: 130 Max: 1

Detail - Optional

Loop: LM Elements: 1

User Option (Usage): Used

Purpose: To transmit standard code list identification information

Comments: 

1. LM02 identifies the applicable industry code list source information.

DLMS Note:

1. Must use this 2/LM/130 loop to identify coded information maintained in department or agency documentation.

2. Use this 2/LM/130 loop for individual modification requests to identify the desired coded data associated with the individual transactions.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

LM01 559 Agency Qualifier Code

Description: Code identifying the agency assigning

the code values

M ID 2/2 Must use

Code Name

DF Department of Defense (DoD)
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 44 March 29, 2024

LQ Industry Code Pos: 140 Max: 100

Detail - Mandatory

Loop: LM Elements: 2

User Option (Usage): Must use

Purpose: Code to transmit standard industry codes

Syntax Rules: 

1. C0102 - If LQ01 is present, then LQ02 is required.

DLMS Note:

Use to identify codes, as appropriate, consistent with management information requirements.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

LQ01 1270 Code List Qualifier Code

Description: Code identifying a specific industry

code list

DLMS Note: The following codes are authorized.

O ID 1/3 Must use

Code Name

0 Document Identification Code

DLMS Note:

1. The MILSTRIP DIC is retained in the DLMS to facilitate transaction conversion in a mixed legacy

MILSTRIP/DLMS environment. Continued support of the DIC in a full DLMS environment will be

assessed at a future date. 

2. Use two iterations to identify requisition DIC and Requisition Exception Data Transaction (DLA DIC

YRZ), when applicable.

3. Future streamlined data; see introductory DLMS note 3c.

1. The MILSTRIP DIC is retained in the DLMS to facilitate transaction conversion in a mixed legacy

MILSTRIP/DLMS environment. Continued support of the DIC in a full DLMS environment will be

assessed at a future date. 

2. Use two iterations to identify requisition DIC and Requisition Exception Data Transaction (DLA DIC

YRZ), when applicable.

3. Future streamlined data; see introductory DLMS note 3c.

67 Type of Assistance Code

DLMS Note:

1. For SA transactions, use when the coded address in the transaction number does not identify the

type of assistance and financing.

2. DLMS enhancement; see introductory DLMS note 3a.

78 Project Code

DLMS Note:

1. Use to modify, or in the case of an unmatched modification, use to identify special programs,

exercises, projects, operations, and other purposes.

2. For DoD SLOA/Accounting Classification compliance the Project Code may be repeated as a Project

Identifier (FA201 Qualifier 90). Refer to ADC 1043.

79 Priority Designator Code

DLMS Note:

Use to modify, or in the case of an unmatched modification, use to identify the priority designator of the

requisition.

80 Advice Code

DLMS Note:

Use to modify, or in the case of an unmatched modification, use to convey information to the supply

source which is considered essential to the supply action.

81 Status Code

DLMS Note:

Used by internet ordering applications to notify DAAS that the requisition modification failed to receive

authorization for continued processing under funds verification procedures. Only Supply Status CX is

applicable. This is an authorized DLMS enhancement. Refer to ADC 328.
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Code Name

004010F511M5MA56 45 March 29, 2024

83 Supply Condition Code

DLMS Note:

1. Use to indicate the lowest acceptable condition of materiel when requisitioning from DLA Disposition

Services.

2. When requisitioning specific reparables for induction under Depot Maintenance Inter-Service

Agreement (DMISA) or comparable inter-Service agreement, cite the supply condition code (SCC)

applicable to the reparable item requested. Authorized SCCs include D, F, G, and Q. Requisitions for

induction of a Product Quality Deficiency Report (PQDR) exhibit for warrantied maintenance will cite

SCC Q. Refer to ADC 1176.

1. Use to indicate the lowest acceptable condition of materiel when requisitioning from DLA Disposition

Services.

2. When requisitioning specific reparables for induction under Depot Maintenance Inter-Service

Agreement (DMISA) or comparable inter-Service agreement, cite the supply condition code (SCC)

applicable to the reparable item requested. Authorized SCCs include D, F, G, and Q. Requisitions for

induction of a Product Quality Deficiency Report (PQDR) exhibit for warrantied maintenance will cite

SCC Q. Refer to ADC 1176.

84 Management Code

DLMS Note:

1. Authorized DLMS enhancement under DLA industrial activity support agreement. (Refer to ADC 352,

ADC 359 and ADC 375)

2. Authorized on an Intra-Air Force basis with BR02 transaction type code AM to provided required

management code information on the reason for the requisition. (Refer to ADC 1390)

87 Subsistence Type of Pack Code

DLMS Note:

Use with subsistence items.

89 Cooperative Logistics Program Support Code

DLMS Note:

For FMS transactions, must use to identify programmed, nonprogrammed, and termination/drawdown

requirements.

94 Identification Code

DLMS Note:

Must use in FMS transactions to identify the customer country's requisitioning Service Code: B, D, K, P,

or T. This is the SA program Customer Service Designator (codes derived from Qualifier 71, Service

and Agency Code).

A data maintenance action was approved in version 5010. The approved code/name is "CSD -

Customer

Service Designator".

Must use in FMS transactions to identify the customer country's requisitioning Service Code: B, D, K, P,

or T. This is the SA program Customer Service Designator (codes derived from Qualifier 71, Service

and Agency Code).

A data maintenance action was approved in version 5010. The approved code/name is "CSD -

Customer

Service Designator".

95 Offer and Release Option Code

DLMS Note:

For FMS transactions, must use to modify, or in the case of an unmatched modification, use to advise

the supply source of the type of notice required prior to shipping the materiel.

97 Ultimate Recipient Code

DLMS Note:

1. Use to identify the buyer of DoD materiel to allow full payment for materiel supplied to a non-DoD

customer.

2. DLMS enhancement; see introductory DLMS note 3a.

99 Purpose Code

DLMS Note:

1. Use in CAV transactions.

2. DLMS enhancement; see introductory DLMS note 3a.

A1 Ownership Code

DLMS Note:

1. Use in requisition or referral order to identify the ownership of previously purchased materiel. This is

a restricted use applicable when a Service has entered into an MOA with DLA relative to Service-owned

stocks, centrally-managed/stored by DLA (1BR06/020, Code RI).

2. Use on a referral order to initiate an inter-Service ammunition or ammunition-related ownership

transfer with no physical movement of materiel. Use to identify the new/gaining (to) ownership code. 

DLMS enhancement. Refer to ADC 1020.

1. Use in requisition or referral order to identify the ownership of previously purchased materiel. This is

a restricted use applicable when a Service has entered into an MOA with DLA relative to Service-owned

stocks, centrally-managed/stored by DLA (1BR06/020, Code RI).

2. Use on a referral order to initiate an inter-Service ammunition or ammunition-related ownership

transfer with no physical movement of materiel. Use to identify the new/gaining (to) ownership code. 

DLMS enhancement. Refer to ADC 1020.
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Code Name

004010F511M5MA56 46 March 29, 2024

3. Also authorized on an intra-Army basis with BR02 Transaction Type Code A0 and BR06 Action Code

J for identification of the ownership of materiel post-post issued by Army Single Stock Fund activities.

A2 Customer Within Country Code

DLMS Note:

1. For SA transactions, use when the coded address in the transaction number does not identify the

customer-within-country.

2. DLMS enhancement; see introductory DLMS note 3a.

A3 Delivery Term Code

DLMS Note:

For FMS transactions, use when the coded address in the transaction number does not identify the

delivery term.

A5 Subcase Number

DLMS Note:

1. Use in FMS transactions based on Service requirements.

2. DLMS enhancement; see introductory DLMS note 3a.

A6 Freight Forwarder Number

DLMS Note:

Must use in FMS transactions to modify, or in the case of an unmatched modification, use to identify the

country representative or freight forwarder to receive shipments and documentation.

A7 Record Control Number

DLMS Note:

Must use in MAP/GA transactions to identify the program line item number.

A8 Program Year Code

DLMS Note:

Must use in MAP/GA transactions to indicate the program year in which the requisitioned item was

approved and funded.

A9 Supplemental Data

DLMS Note:

1. Use to identify, or to modify, supplementary address/supplemental data.

2. During the legacy MILSTRIP/DLMS transition, this field will be used to perpetuate/populate the

MILSTRIP Supplementary Address (SUPADD) field. During this time, field size is restricted to 6

positions; see introductory DLMS note 3d.

3. Expanded use of this field for supplemental data without size restriction is a DLMS enhancement; see

introductory DLMS note 3a.

4. Under full DLMS, the requirement to pass activity address information within the supplemental data

field will be streamlined. Activity address data previously contained in the SUPADD will be reflected

exclusively in the N1 segment. Future streamlined data; see introductory DLMS note 3c.

5. During legacy MILSTRIP/DLMS transition, use on a referral order modification to initiate an

inter-Service ammunition or ammunition-related ownership transfer with no physical movement of

materiel and no billing. Cite Signal Code M and Project Code CYK in conjunction with the supplemental

data field constructed as follows: Service/Agency Code Y followed by the old (from) ownership code,

the RIC to which ownership is transferred, and the new/gaining (to) ownership code. Refer to ADC

1020.

1. Use to identify, or to modify, supplementary address/supplemental data.

2. During the legacy MILSTRIP/DLMS transition, this field will be used to perpetuate/populate the

MILSTRIP Supplementary Address (SUPADD) field. During this time, field size is restricted to 6

positions; see introductory DLMS note 3d.

3. Expanded use of this field for supplemental data without size restriction is a DLMS enhancement; see

introductory DLMS note 3a.

4. Under full DLMS, the requirement to pass activity address information within the supplemental data

field will be streamlined. Activity address data previously contained in the SUPADD will be reflected

exclusively in the N1 segment. Future streamlined data; see introductory DLMS note 3c.

5. During legacy MILSTRIP/DLMS transition, use on a referral order modification to initiate an

inter-Service ammunition or ammunition-related ownership transfer with no physical movement of

materiel and no billing. Cite Signal Code M and Project Code CYK in conjunction with the supplemental

data field constructed as follows: Service/Agency Code Y followed by the old (from) ownership code,

the RIC to which ownership is transferred, and the new/gaining (to) ownership code. Refer to ADC

1020.

AJ Utilization Code

DLMS Note:

1. Use to identify a specialized purpose for which the requisition is submitted.

2. Under legacy MILSTRIP, this is the first position of the document serial number within the document

number.

3. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

4. DLMS enhancement; see introductory DLMS note.
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Code Name

004010F511M5MA56 47 March 29, 2024

AK Distribution Code

DLMS Note:

1. Use to modify, or in the case of an unmatched modification, use to identify the distribution code. 

Modifier transactions may not be used to change this field for Government Furnished Materiel (GFM)

requisitions.

2. Future streamlined data; see introductory DLMS note 3c.

AL Special Requirements Code

DLMS Note:

1. Under legacy MILSTRIP, this is carried in the required delivery date field.

2. DLMS enhancement; see introductory DLMS note 3a.

3. Use in conjunction with 2/LQ01/Code RC, Requirement Code, to complete the Air Force unique

NMCS/MICAP data requirement.

BD Transportation Priority Code

DLMS Note:

1. Use to identify a transportation priority which is different than that associated with the requisition

priority.

2. DLMS enhancement; see introductory DLMS note 3a.

DE Signal Code

DLMS Note:

1. Use to modify, or in the case of an unmatched modification, use to identify the signal code. Modifier

transactions may not be used to change this field for Government Furnished Materiel (GFM)

requisitions.

2. Future streamlined data; see introductory DLMS note 3c.

DF Media and Status Code

DLMS Note:

1. Use to modify, or in the case of an unmatched modification, use to identify the media and status

code. Modifier transactions may not be used to change this field for Government Furnished Materiel

(GFM) requisitions.

2. Future streamlined data; see introductory DLMS note 3c.

DJ Remedial Action Code

DLMS Note:

Use temporary qualifier DJ - Remedial Action Code to identify Army Edit Action Code indicating the

actions required by the receiving system in order to accurately process transactions and direct the

types of follow-on actions authorized to occur. This is an Army unique data element, and is meaningful

to the Army only. The code source is identified as the U.S. Army Materiel Command Single Stock Fund

Functional User Manual, 3rd Edition. An ANSI data maintenance request has been prepared to

establish a new data element 1270 code qualifier assignment for Army Edit Action Code.

Use temporary qualifier DJ - Remedial Action Code to identify Army Edit Action Code indicating the

actions required by the receiving system in order to accurately process transactions and direct the

types of follow-on actions authorized to occur. This is an Army unique data element, and is meaningful

to the Army only. The code source is identified as the U.S. Army Materiel Command Single Stock Fund

Functional User Manual, 3rd Edition. An ANSI data maintenance request has been prepared to

establish a new data element 1270 code qualifier assignment for Army Edit Action Code.

GQ Group Qualifier Code

DLMS Note:

Use to identify the Materiel Management Aggregation Code (MMAC) for NSNs to be managed by a

specific manager (i.e., system, program, aggregation, selected FSC, technology group). This is an Air

Force-unique data element, meaningful to the Air Force only. Non-Air Force Components perpetuate

without action.

A data maintenance action was approved in version 5010. The approved code/name is "MAC – Material

Management Aggregation Code". The code source is identified as the Air Force Manual (AFMAN)

23-110, Volumes 1 and 2.

Use to identify the Materiel Management Aggregation Code (MMAC) for NSNs to be managed by a

specific manager (i.e., system, program, aggregation, selected FSC, technology group). This is an Air

Force-unique data element, meaningful to the Air Force only. Non-Air Force Components perpetuate

without action.

A data maintenance action was approved in version 5010. The approved code/name is "MAC – Material

Management Aggregation Code". The code source is identified as the Air Force Manual (AFMAN)

23-110, Volumes 1 and 2.

KJ Assured Delivery Indicator

DLMS Note:

1. Use to identify, or modify, the Delivery Priority/Special Processing Code for materiel that has an

urgency of need within the maintenance shop and must be delivered within one hour of receipt of the

issue request. Value will be X (1 hour issue) when applicable.
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Code Name

004010F511M5MA56 48 March 29, 2024

2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

3. A data maintenance action was approved in version 5030. The approved code/name is DPC –

Delivery Priority Code. DoD systems will continue to use Qualifier KJ to represent the Delivery

Priority/Special Processing Code until such time as a new ADC directs otherwise.

RC Requirement Code

DLMS Note:

1. Use to identify the Air Force Urgency Justification Code indicating the urgency of need and type of

requirement (justification) related to a Not Mission Capable Supply/Mission Impaired Capability Awaiting

Parts (NMCS/MICAP) condition.

2. Use in conjunction with Special Requirements Code N (2/LQ01/Code AL or perpetuated from legacy

MILSTRIP Required Delivery Date field). This is an Air Force unique data element, meaningful to the

Air Force only. Non-Air Force Components perpetuate without action. The code source is identified as

the Air Force Manual (AFMAN) 23-110, Volume 1 and 2.

A data maintenance action was approved in version 5010. The approved code/name is "UJC - Urgency

Justification Code".

1. Use to identify the Air Force Urgency Justification Code indicating the urgency of need and type of

requirement (justification) related to a Not Mission Capable Supply/Mission Impaired Capability Awaiting

Parts (NMCS/MICAP) condition.

2. Use in conjunction with Special Requirements Code N (2/LQ01/Code AL or perpetuated from legacy

MILSTRIP Required Delivery Date field). This is an Air Force unique data element, meaningful to the

Air Force only. Non-Air Force Components perpetuate without action. The code source is identified as

the Air Force Manual (AFMAN) 23-110, Volume 1 and 2.

A data maintenance action was approved in version 5010. The approved code/name is "UJC - Urgency

Justification Code".

RD Property Ownership Type Code

DLMS Note:

Use only on a referral order modification to initiate an inter-Service ammunition or ammunition-related

ownership transfer with no physical movement of materiel. Use to identify, or to modify, the old (from)

ownership code. DLMS enhancement. Refer to ADC 1020.

COG Cognizance Symbol

DLMS Note:

1. Use to identify the material cognizance symbol (COG) of the end item. Indicate NSL for non-stock

numbered listed items. This is a Navy-unique data element meaningful to Navy only; Non-Navy

Components are to perpetuate without action.

2. DLMS enhancement.

DSI Disposition Services Indicator

DLMS Note:

1. DLA Disposition Services uses to provide (or modify) relevant information applicable to the DLA

Disposition Services business process supported by this transaction on an intra-DLA basis. Use

multiple repetitions of the LQ Segment to include all applicable codes. Authorized DLMS enhancement

for use by DLA Disposition Services. Refer to ADC 466.

2. The following Disposition Services Indicator values are available for use in the requisition transaction:

 MRA – Materiel Receipt Acknowledgment Required. 

 DMIL – DEMIL Certification Required. 

 MUTL – Mutilation Certification Required. 

 RCYL – Certificate of Recycling Required. 

 CIF – Container Issued in Full. 

 WALK – Walk-in Customer. 

 PICK – Customer Pick-up Required.

 CS – DEMIL Condition of Sale Indicator

3. At this time a local code ‘DSI’ is established for use in 511M, version 4010. A data maintenance

action has been submitted for establishment of ‘DSI-Disposition Services Indicator’ in a future version.

1. DLA Disposition Services uses to provide (or modify) relevant information applicable to the DLA

Disposition Services business process supported by this transaction on an intra-DLA basis. Use

multiple repetitions of the LQ Segment to include all applicable codes. Authorized DLMS enhancement

for use by DLA Disposition Services. Refer to ADC 466.

2. The following Disposition Services Indicator values are available for use in the requisition transaction:

 MRA – Materiel Receipt Acknowledgment Required. 

 DMIL – DEMIL Certification Required. 

 MUTL – Mutilation Certification Required. 

 RCYL – Certificate of Recycling Required. 

 CIF – Container Issued in Full. 

 WALK – Walk-in Customer. 

 PICK – Customer Pick-up Required.

 CS – DEMIL Condition of Sale Indicator

3. At this time a local code ‘DSI’ is established for use in 511M, version 4010. A data maintenance

action has been submitted for establishment of ‘DSI-Disposition Services Indicator’ in a future version.

EWR Evaluate Work Candidate Reason Lookup

DLMS Note:

1. Use to identify, or to modify, the Requirement Churn Reason Code to identify materiel orders

required by the industrial site to complete planned work above what was originally identified during the

pre-planned process, ordered and delivered after the start of the availability.

2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

IMC Item Management Code

DLMS Note:

1. Use to identify the Item Management Code (IMC) for integrated material management. This is a

Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without

action.
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Code Name

004010F511M5MA56 49 March 29, 2024

2. DLMS enhancement.

MCC Material Control Code

DLMS Note:

1. Use to identify the Material Control Code (MCC) for special inventory reporting. This is a

Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without

action.

2. DLMS enhancement.

SEC Stock Exchange Code

DLMS Note:

Use to identify the Exchange Pricing Indicator for intra-Army transactions to identify that the Customer

and NIIN on the transaction are Exchange Pricing relevant. When applicable, cite code value EP

(Exchange Pricing). Refer to ADC 274.

A data maintenance action was approved in version 6010. The approved code/name is "EPI –

Exchange Pricing Indicator".

SMI Special Material Identification Code

DLMS Note:

1. Use to identify the Special Material Identification Code (SMIC) for an end item. This is a

Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without

action.

2. DLMS enhancement.

T05 Inspection Parameters

DLMS Note:

1. Use to identify, or to modify, the Quality Inspection Code indicating the level of quality inspection to

which the item must be procured and inspected. 

2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

LQ02 1271 Industry Code

Description: Code indicating a code from a specific

industry code list

X AN 1/30 Must use
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 50 March 29, 2024

QTY Quantity Pos: 150 Max: 1

Detail - Optional

Loop: QTY Elements: 2

User Option (Usage): Used

Purpose: To specify quantity information

Syntax Rules: 

1. R0204 - At least one of QTY02 or QTY04 is required.

2. E0204 - Only one of QTY02 or QTY04 may be present.

Semantics: 

1. QTY04 is used when the quantity is non-numeric.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

QTY01 673 Quantity Qualifier

Description: Code specifying the type of quantity

M ID 2/2 Must use

Code Name

OC Order Count

DLMS Note:

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.

QTY02 380 Quantity

Description: Numeric value of quantity

DLMS Note: Express as a whole number with no

decimal. 

X R 1/15 Must use
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 51 March 29, 2024

N1 Name Pos: 180 Max: 1

Detail - Optional

Loop: N1 Elements: 5

User Option (Usage): Used

Purpose: To identify a party by type of organization, name, and code

Syntax Rules: 

1. R0203 - At least one of N102 or N103 is required.

2. P0304 - If either N103 or N104 is present, then the other is required.

Comments: 

1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID

Code" (N104) must provide a key to the table maintained by the transaction processing party.

2. N105 and N106 further define the type of entity in N101.

DLMS Note:

1. Must use one iteration of this 2/N1/180 loop to identify the organization to receive the transaction.

2. Use additional iterations to identify other organizations associated with the transaction.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

N101 98 Entity Identifier Code

Description: Code identifying an organizational

entity, a physical location, property or an individual

DLMS Note: The following codes are authorized.

M ID 2/3 Must use

Code Name

BG Buying Group

DLMS Note:

1. Use to identify the G-Invoicing Group Name Description. Refer ADC 1465.

2. DLMS enhancement; see introductory DLMS note 3a.

BS Bill and Ship To

DLMS Note:

Use either this code, or both codes BT and ST, for reimbursable materiel. Use to modify, or in the case

of an unmatched modification, use to identify the organization which receives both the materiel and the

billing for the materiel. Modifier transactions may not be used to change this field for GFM requisitions.

BT Bill-to-Party

DLMS Note:

1. Use with code ST for reimbursable materiel. Use to modify, or in the case of an unmatched

modification, use to identify the organization to receive billing for materiel when different form the

organization receiving the materiel. Use precludes the use of Code BS for the Bill-to DoDAAC. Modifier

transactions may not be used to change this field for GFM requisitions.

2. Use for SFIS compliant systems to identify the BPN of the party to receive the bill. 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.

3. Authorized DLMS enhancement; see introductory DLMS note 3g.

1. Use with code ST for reimbursable materiel. Use to modify, or in the case of an unmatched

modification, use to identify the organization to receive billing for materiel when different form the

organization receiving the materiel. Use precludes the use of Code BS for the Bill-to DoDAAC. Modifier

transactions may not be used to change this field for GFM requisitions.

2. Use for SFIS compliant systems to identify the BPN of the party to receive the bill. 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.

3. Authorized DLMS enhancement; see introductory DLMS note 3g.

DA Delivery Address

DLMS Note:

1. Use with 2/N2/190, 2/N3/200, and 2/N4/210 to fully identify or modify in-the-clear exception ship-to

address information under authorized conditions.

2. Use for Requisition Exception Data Transaction (DLA DIC YRZ-Transaction Code ST) for exception 
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Code Name

004010F511M5MA56 52 March 29, 2024

ship-to address information. See introductory DLMS note 3f.

3. DLMS enhancement; see introductory DLMS note 3a.

DZ Delivery Zone

DLMS Note:

1. Use to provide the DELIVERY LOCATION indicating where the materiel is to be staged/stored. 

2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

IF International Freight Forwarder

DLMS Note:

Use for Requisition Exception Data Transaction (DLA DIC YRZ-Transaction Code NA) Notice of

Availability (NOA) address information. See introductory DLMS note 3f.

MF Manufacturer of Goods

PK Party to Receive Copy

DLMS Note:

1. Use as needed to identify an organization to be provided a copy of this transaction. Use with N103,

qualifier M4 (Routing Identifier) and N106, qualifier To (Message To).

2. Must be used between Army and DLA for their integrated set assembly program, when an assembly

component part being ordered by the Army is not managed by DLA, and DLA is acquiring it in support

of the Army medical mission. Refer to ADC 276.

3. Used between Navy and DLA for Navy requisitions submitted directly to other Component SoS, so

that DLA will be able to support follow-on actions on behalf of the Navy industrial activity (IA) under a

DLA industrial activity support agreement. Refer to ADC 377.

4. DLMS enhancement; see introductory DLMS Note 3a.

1. Use as needed to identify an organization to be provided a copy of this transaction. Use with N103,

qualifier M4 (Routing Identifier) and N106, qualifier To (Message To).

2. Must be used between Army and DLA for their integrated set assembly program, when an assembly

component part being ordered by the Army is not managed by DLA, and DLA is acquiring it in support

of the Army medical mission. Refer to ADC 276.

3. Used between Navy and DLA for Navy requisitions submitted directly to other Component SoS, so

that DLA will be able to support follow-on actions on behalf of the Navy industrial activity (IA) under a

DLA industrial activity support agreement. Refer to ADC 377.

4. DLMS enhancement; see introductory DLMS Note 3a.

ST Ship To

DLMS Note:

Use with code BT for reimbursable materiel. Use to modify, or in the case of an unmatched

modification, use to identify the organization to receive the materiel when different from the activity

being billed for the materiel. Use precludes the use of Code BS. Modifier transactions may not be

used to change this field for GFM requisitions.

UQ Subsequent Owner

DLMS Note:

Use only on a referral order modification to initiate an inter-Service ammunition or ammunition-related

ownership transfer with no physical movement of materiel. Use to identify, or to modify, the RIC to

which ownership is being transferred (the New Owner RIC). DLMS enhancement. Refer to ADC 1020.

XN Planning/Maintenance Organization

DLMS Note:

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.

Z1 Party to Receive Status

DLMS Note:

1. Use to modify, or in the case of an unmatched modification, use to identify the party to receive status

when different from Service/Agency prescribed status recipient. Use multiple iterations to identify all

status recipients, as required.

2. The DLMS provides the capability to carry additional status recipients beyond those identified by

legacy MILSTRIP. The Media and Status Code and the Distribution Code will be retained in the DLMS

to facilitate transaction conversion in a mixed legacy MILSTRIP/DLMS environment. Additional status

recipients identified here cannot be passed to legacy MILSTRIP users.

1. Use to modify, or in the case of an unmatched modification, use to identify the party to receive status

when different from Service/Agency prescribed status recipient. Use multiple iterations to identify all

status recipients, as required.

2. The DLMS provides the capability to carry additional status recipients beyond those identified by

legacy MILSTRIP. The Media and Status Code and the Distribution Code will be retained in the DLMS

to facilitate transaction conversion in a mixed legacy MILSTRIP/DLMS environment. Additional status

recipients identified here cannot be passed to legacy MILSTRIP users.

Z2 Unserviceable Material Consignee

DLMS Note:

Use when requisitioning from a reclamation organization to indicate the consignee for unserviceable 
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Code Name

004010F511M5MA56 53 March 29, 2024

materiel.

Z3 Potential Source of Supply

DLMS Note:

Use when requisitioning nonstandard materiel identified in PO106 only with code FT or MG to identify

potential supply sources.

Z4 Owning Inventory Control Point

DLMS Note:

Must use to identify the owning ICP.

Z5 Management Control Activity

DLMS Note:

Use for GFM or CFM requisitions.

Z7 Mark-for Party

DLMS Note:

1. Use to identify or modify 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 3g. Refer to ADC 1009A.

5. Also use for Requisition Exception Data Transaction (DLA DIC YRZ-Transaction Code MF) to identify

mark-for delivery information. See introductory DLMS note 3f.

1. Use to identify or modify 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 3g. Refer to ADC 1009A.

5. Also use for Requisition Exception Data Transaction (DLA DIC YRZ-Transaction Code MF) to identify

mark-for delivery information. See introductory DLMS note 3f.

003 Application Party

DLMS Note:

Used with Supply Status CX to identify the Routing Identifier of the internet ordering application in

notification to DAAS that the requisition modifier failed to receive authorization for continued processing

under funds verification procedures. DAAS shall prepare CX Supply Status on behalf of the identified

internet ordering application rather than continue processing the requisition modifier. Refer to ADC 328.

IAD Foreign Office

DLMS Note:

1. Use for clear-text exception data FMS in-country address.

2. Use for Requisition Exception Data Transaction (DLA DIC YRZ-Transaction Code MA) FOR FMS

in-country mark-for address. See introductory DLMS note 3f.

N102 93 Name

Description: Free-form name

DLMS Note: 1. Use with 2/N1/180 N101 code MF to

identify the manufacturer's name when the CAGE

code is not available. When the CAGE code is

available use N103 and N104.

2. Use with 2/N1/180 N101 code DA to identify the

exception ship-to organization.

3. Use with N101 Code Z7 to identify the recipient of

materiel. Total field length is restricted to 24 clear

text characters, when not used in combination with a

DoDAAC or RIC. If combined with a Mark-for

DoDAAC, restrict clear text to 17 characters. If

combined with a Mark-for RIC, restrict clear text to

20 characters. Authorized DLMS enhancement; see

introductory DLMS note 3g. Refer to ADC 1009A.

3. Use with N101 Code Z7 to identify the recipient of

materiel. Total field length is restricted to 24 clear

text characters, when not used in combination with a

DoDAAC or RIC. If combined with a Mark-for

DoDAAC, restrict clear text to 17 characters. If

combined with a Mark-for RIC, restrict clear text to

20 characters. Authorized DLMS enhancement; see

introductory DLMS note 3g. Refer to ADC 1009A.

X AN 1/60 Used
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004010F511M5MA56 54 March 29, 2024

4. Use for Requisition Exception Data Transaction

(DLA DIC YRZ- Transaction Codes ST, MA, NA and

MF) with N101 code DA, IAD, IF and Z7 to identify

the exception address line 1. For Codes DA, IAD

and IF a maximum of 35 positions (including

spaces) is allowed. For code Z7 a maximum of 30

positions (including spaces) is allowed. See

introductory DLMS notes 3f.

4. Use for Requisition Exception Data Transaction

(DLA DIC YRZ- Transaction Codes ST, MA, NA and

MF) with N101 code DA, IAD, IF and Z7 to identify

the exception address line 1. For Codes DA, IAD

and IF a maximum of 35 positions (including

spaces) is allowed. For code Z7 a maximum of 30

positions (including spaces) is allowed. See

introductory DLMS notes 3f.

5. Use to identify the delivery location (Qualifier DZ,

2/N101/180). Field length is 30 positions maximum.

6. Use with N101 Code BG to identify the

G-Invoicing Group Name Description. The format for

DoD Components is the DoDAAC followed by a

hyphen; followed by the DoDAAC description. Refer

to ADC 1465.

N103 66 Identification Code Qualifier

Description: Code designating the system/method

of code structure used for Identification Code (67)

X ID 1/2 Used

Code Name

10 Department of Defense Activity Address Code (DODAAC)

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

33 Commercial and Government Entity (CAGE)

50 Business License Number

DLMS Note:

1. Use for SFIS to map to SFIS Data element “Business Partner Number TP3”. Enter the buyer’s BPN

in N104. 

2. Authorized DLMS enhancement; see introductory DLMS note 3g.

92 Assigned by Buyer or Buyer's Agent

DLMS Note:

Use with N101 Code XN to identify the user assigned Shop Service Center/Shop Store Identifier. Refer

to ADCs 284A, 381, and 1454.

A2 Military Assistance Program Address Code (MAPAC)

DLMS Note:

1. Use to indicate the Security Assistance (SA) structured address data.

2. DLMS enhancement; see introductory DLMS note 3a. 

M4 Department of Defense Routing Identifier Code (RIC)

N104 67 Identification Code

Description: Code identifying a party or other code

X AN 2/80 Used

N106 98 Entity Identifier Code

Description: Code identifying an organizational

entity, a physical location, property or an individual

O ID 2/3 Used

Code Name

TO Message To

DLMS Note:

Must use with the appropriate 2/N101/180 code to indicate the organization cited in N104 is receiving

the transaction.
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 55 March 29, 2024

N2 Additional Name Information Pos: 190 Max: 2

Detail - Optional

Loop: N1 Elements: 2

User Option (Usage): Used

Purpose: To specify additional names or those longer than 35 characters in length

DLMS Note:

1. Use to identify additional name information as authorized.

2. Use with 2/N101/180 code DA to identify additional in-the-clear exception ship-to name information, with code MF to identify the

manufacturer's name information, and with code ST to identify additional ship-to name information for excess plant property.

3. Use for Requisition Exception Data Transaction (DLA DIC YRZ) for mark-for, ship-to, FMS in-country mark-for and notice of availability

address information. See introductory DLMS note 3f.

4. DLMS enhancement; see introductory DLMS note 3a.

1. Use to identify additional name information as authorized.

2. Use with 2/N101/180 code DA to identify additional in-the-clear exception ship-to name information, with code MF to identify the

manufacturer's name information, and with code ST to identify additional ship-to name information for excess plant property.

3. Use for Requisition Exception Data Transaction (DLA DIC YRZ) for mark-for, ship-to, FMS in-country mark-for and notice of availability

address information. See introductory DLMS note 3f.

4. DLMS enhancement; see introductory DLMS note 3a.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

N201 93 Name

Description: Free-form name

DLMS Note: Use for Requisition Exception Data

Transaction (DLA DIC YRZ-Transaction Codes ST,

MA, NA and MF) with N101 Codes DA, IAD, and IF 

for address line 2, if not the final line and with Z7 for

address line 2. For Codes DA, IAD and IF a

maximum of 35 positions (including spaces) is

allowed. For code Z7 a maximum of 30 positions

(including spaces) is allowed. See introductory

DLMS note 3f.

DLMS Note: Use for Requisition Exception Data

Transaction (DLA DIC YRZ-Transaction Codes ST,

MA, NA and MF) with N101 Codes DA, IAD, and IF 

for address line 2, if not the final line and with Z7 for

address line 2. For Codes DA, IAD and IF a

maximum of 35 positions (including spaces) is

allowed. For code Z7 a maximum of 30 positions

(including spaces) is allowed. See introductory

DLMS note 3f.

M AN 1/60 Must use

N202 93 Name

Description: Free-form name

DLMS Note: Use for Requisition Exception Data

Transaction (DLA DIC YRZ-Transaction Codes ST,

MA, NA and MF) with N101 Codes DA, IAD, and IF 

for address line 3, if not the final line and with Z7 for

address line 3. For Codes DA, IAD and IF a

maximum of 35 positions (including spaces) is

allowed. For code Z7 a maximum of 30 positions

(including spaces) is allowed. See introductory

DLMS note 3f.

DLMS Note: Use for Requisition Exception Data

Transaction (DLA DIC YRZ-Transaction Codes ST,

MA, NA and MF) with N101 Codes DA, IAD, and IF 

for address line 3, if not the final line and with Z7 for

address line 3. For Codes DA, IAD and IF a

maximum of 35 positions (including spaces) is

allowed. For code Z7 a maximum of 30 positions

(including spaces) is allowed. See introductory

DLMS note 3f.

O AN 1/60 Used
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 56 March 29, 2024

N3 Address Information Pos: 200 Max: 2

Detail - Optional

Loop: N1 Elements: 1

User Option (Usage): Used

Purpose: To specify the location of the named party

DLMS Note:

1. Use to identify additional address information as authorized.

2. Use with 2/N101/180 code DA to identify additional in-the-clear exception ship-to address information, with code MF to identify the

manufacturer's geographical location information.

3. Use for Requisition Exception Data Transaction (DLA DIC YRZ) for mark-for delivery data. See introductory DLMS note 3f.

4. DLMS enhancement; see introductory DLMS note 3a.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

N301 166 Address Information

Description: Address information

DLMS Note: Use for Requisition Exception Data

Transaction (DLA DIC YRZ- Transaction Code MF)

with N101 code Z7 to reflect line 4 of the mark-for

delivery data. A maximum of 30 positions (including

spaces) is allowed. 

DLMS Note: Use for Requisition Exception Data

Transaction (DLA DIC YRZ- Transaction Code MF)

with N101 code Z7 to reflect line 4 of the mark-for

delivery data. A maximum of 30 positions (including

spaces) is allowed. 

M AN 1/55 Must use
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 57 March 29, 2024

N4 Geographic Location Pos: 210 Max: 1

Detail - Optional

Loop: N1 Elements: 4

User Option (Usage): Used

Purpose: To specify the geographic place of the named party

Syntax Rules: 

1. C0605 - If N406 is present, then N405 is required.

Comments: 

1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.

2. N402 is required only if city name (N401) is in the U.S. or Canada.

DLMS Note:

1. Use with 2/N101/180 code DA to identify in-the-clear exception ship-to geographic location information, with code MF to identify the

manufacturer's geographical location information, and with code ST to provide the geographical location ship-to information for excess plant

property.

2. Use for Requisition Exception Data Transaction to reflect address information. See introductory DLMS note 3f.

3. DLMS enhancement; see introductory DLMS note 3a.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

N401 19 City Name

Description: Free-form text for city name

DLMS Note: Use for Requisition Exception Data

Transaction (DLA DIC YRZ-Transaction Codes ST,

MA and NA) with N101 Codes DA, IF, and IAD for

final address line to reflect the city name. (DLA DIC

YRZ-City Name in field positions 22-41). A

maximum of 20 positions (including spaces) is

allowed. See introductory DLMS note 3f.

DLMS Note: Use for Requisition Exception Data

Transaction (DLA DIC YRZ-Transaction Codes ST,

MA and NA) with N101 Codes DA, IF, and IAD for

final address line to reflect the city name. (DLA DIC

YRZ-City Name in field positions 22-41). A

maximum of 20 positions (including spaces) is

allowed. See introductory DLMS note 3f.

O AN 2/30 Used

N402 156 State or Province Code

Description: Code (Standard State/Province) as

defined by appropriate government agency

DLMS Note: Use for Requisition Exception Data

Transaction (DLA DIC YRZ-Transaction Code ST)

with N101 code DA and IF for final address line to

indicate the state code associated with the ship to

address, when applicable. (DLA DIC YRZ-State

Code in field positions 43-44).

DLMS Note: Use for Requisition Exception Data

Transaction (DLA DIC YRZ-Transaction Code ST)

with N101 code DA and IF for final address line to

indicate the state code associated with the ship to

address, when applicable. (DLA DIC YRZ-State

Code in field positions 43-44).

O ID 2/2 Used

N403 116 Postal Code

Description: Code defining international postal

zone code excluding punctuation and blanks (zip

code for United States)

DLMS Note: Use for the Requisition Exception Data

Transaction (DLA DIC YRZ-Transaction Codes ST,

MA, and NA) with the N101 Codes DA, IF, and IAD

for final address line to reflect the postal code. (DLA

DIC YRZ-Postal Code in field positions 46-56). A

maximum of 11 positions (including spaces) is

allowed. See introductory DLMS note 3f.

DLMS Note: Use for the Requisition Exception Data

Transaction (DLA DIC YRZ-Transaction Codes ST,

MA, and NA) with the N101 Codes DA, IF, and IAD

for final address line to reflect the postal code. (DLA

DIC YRZ-Postal Code in field positions 46-56). A

maximum of 11 positions (including spaces) is

allowed. See introductory DLMS note 3f.

O ID 3/15 Used

N404 26 Country Code O ID 2/3 Used
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004010F511M5MA56 58 March 29, 2024

Description: Code identifying the country

DLMS Note: 1. Use to identify the country. See

introductory DLMS note 5 (Refer to ADC 1075 for

implementation).

2. Use for the Requisition Exception Data

Transaction (DLA DIC YRZ-Transaction Codes ST,

MA and NA) with the N101 Codes DA and IF (when

other than U.S.), and IAD for final address line to

reflect the country code. May reflect DLA 3-position

country code, until ADC 1075 is implemented (April

1, 2014). (DLA DIC YRZ-Country Code in field

positions 43-45). See Introductory DLMS note 3f.

2. Use for the Requisition Exception Data

Transaction (DLA DIC YRZ-Transaction Codes ST,

MA and NA) with the N101 Codes DA and IF (when

other than U.S.), and IAD for final address line to

reflect the country code. May reflect DLA 3-position

country code, until ADC 1075 is implemented (April

1, 2014). (DLA DIC YRZ-Country Code in field

positions 43-45). See Introductory DLMS note 3f.
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 59 March 29, 2024

REF Reference Identification Pos: 220 Max: 1

Detail - Optional

Loop: REF Elements: 3

User Option (Usage): Used

Purpose: To specify identifying information

Syntax Rules: 

1. R0203 - At least one of REF02 or REF03 is required.

Semantics: 

1. REF04 contains data relating to the value cited in REF02.

DLMS Note:

1. At this time, this loop is not authorized for use to provide IUID information. A PDC must be submitted and approved, documenting the

requirement and procedures before using this transaction for transmitting IUID. All references to IUID data are placeholders for future use.

2. Use the 2/REF/220 loop in requisition modification transactions to supplement materiel identification in LIN03 of the 2/LIN/100 when

requisitioning a specific item(s) identified by IUID.

3. This segment will supports item identification based upon the UII or the serial number.

4. This segment also provides for use of a batch/lot number, when applicable.

5. If UII and serial number, and/or batch/lot number are required for the item, enter the UII in REF01, and enter the serial number and/or

batch/lot number in the subsequent N9 segment. If UII is not used, enter the serial number in REF01 and enter the batch/lot number in the

subsequent N9 segment. If only batch/lot number is required, enter the batch/lot number in REF01.

6. The entire 2/REF/220 loop is a DLMS enhancement. See introductory DLMS note 3a.

1. At this time, this loop is not authorized for use to provide IUID information. A PDC must be submitted and approved, documenting the

requirement and procedures before using this transaction for transmitting IUID. All references to IUID data are placeholders for future use.

2. Use the 2/REF/220 loop in requisition modification transactions to supplement materiel identification in LIN03 of the 2/LIN/100 when

requisitioning a specific item(s) identified by IUID.

3. This segment will supports item identification based upon the UII or the serial number.

4. This segment also provides for use of a batch/lot number, when applicable.

5. If UII and serial number, and/or batch/lot number are required for the item, enter the UII in REF01, and enter the serial number and/or

batch/lot number in the subsequent N9 segment. If UII is not used, enter the serial number in REF01 and enter the batch/lot number in the

subsequent N9 segment. If only batch/lot number is required, enter the batch/lot number in REF01.

6. The entire 2/REF/220 loop is a DLMS enhancement. See introductory DLMS note 3a.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

REF01 128 Reference Identification Qualifier

Description: Code qualifying the Reference

Identification

M ID 2/3 Must use

Code Name

BT Batch Number

DLMS Note:

Use to identify the manufacturer's batch/lot number or other number identifying the production run when

UII and/or serial number are not required. If UII and/or serial number are required in addition to the

batch/lot number, enter the batch/lot number in N901.

SE Serial Number

DLMS Note:

Use to identify the serial number when UII is not required. If UII is required in addition to the serial

number, enter serial number in N901.

U3 Unique Supplier Identification Number (USIN)

DLMS Note:

Use to identify the UII. Place UII value in REF03. A data maintenance action was approved in version

5020. The approved code/name is "UII - Department of Defense Unique Item Identifier".

REF02 127 Reference Identification

Description: Reference information as defined for a

particular Transaction Set or as specified by the

Reference Identification Qualifier

DLMS Note: For use with REF01 codes BT and SE.

X AN 1/30 Used

REF03 352 Description X AN 1/80 Used
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004010F511M5MA56 60 March 29, 2024

Description: A free-form description to clarify the

related data elements and their content

DLMS Note: Use to indicate UII value when

REF01=U3.
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 61 March 29, 2024

N9 Reference Identification Pos: 240 Max: >1

Detail - Optional

Loop: REF Elements: 2

User Option (Usage): Used

Purpose: To transmit identifying information as specified by the Reference Identification Qualifier

Syntax Rules: 

1. R0203 - At least one of N902 or N903 is required.

2. C0605 - If N906 is present, then N905 is required.

Semantics: 

1. N906 reflects the time zone which the time reflects.

2. N907 contains data relating to the value cited in N902.

DLMS Note:

1. Use multiple repetitions to identify the characteristic(s) not defined in the 2/REF/220 segment.

2. DLMS enhancement; see introductory DLMS note 3a.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

N901 128 Reference Identification Qualifier

Description: Code qualifying the Reference

Identification

DLMS Note: The following codes are used to

identify the characteristic not defined in the

2/REF/220 segment.

M ID 2/3 Must use

Code Name

BT Batch Number

DLMS Note:

Use to identify the manufacturer's batch/lot number or other number identifying the production run,

when UII or serial number is entered in REF01, and batch/lot is also used.

SE Serial Number

DLMS Note:

Use to identify the serial number when UII is entered in REF01 and serial number is also used.

N902 127 Reference Identification

Description: Reference information as defined for a

particular Transaction Set or as specified by the

Reference Identification Qualifier

X AN 1/30 Must use
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 62 March 29, 2024

N1 Name Pos: 250 Max: 1

Detail - Optional

Loop: REF Elements: 3

User Option (Usage): Used

Purpose: To identify a party by type of organization, name, and code

Syntax Rules: 

1. R0203 - At least one of N102 or N103 is required.

2. P0304 - If either N103 or N104 is present, then the other is required.

Comments: 

1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID

Code" (N104) must provide a key to the table maintained by the transaction processing party.

2. N105 and N106 further define the type of entity in N101.

DLMS Note:

1. Use to identify the manufacturer of the UIT item.

2. DLMS enhancement; see introductory DLMS note 3a.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

N101 98 Entity Identifier Code

Description: Code identifying an organizational

entity, a physical location, property or an individual

M ID 2/3 Must use

Code Name

MF Manufacturer of Goods

N103 66 Identification Code Qualifier

Description: Code designating the system/method

of code structure used for Identification Code (67)

X ID 1/2 Must use

Code Name

33 Commercial and Government Entity (CAGE)

N104 67 Identification Code

Description: Code identifying a party or other code

X AN 2/80 Must use
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 63 March 29, 2024

FA1 Type of Financial Accounting Data Pos: 285 Max: 1

Detail - Optional

Loop: FA1 Elements: 2

User Option (Usage): Used

Purpose: To specify the organization controlling the content of the accounting citation, and the purpose associated with the accounting citation

Semantics: 

1. FA101 Identifies the organization controlling the assignment of financial accounting information.

2. FA102 Identifies the purpose of the accounting allowance or charge information.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

FA101 559 Agency Qualifier Code

Description: Code identifying the agency assigning

the code values

DLMS Note: This data element is required for X12

syntax. Select the code that corresponds to the

organization that is responsible for the assignment

of the DoDAAC used to construct the controlling

document number for the transaction.

DLMS Note: This data element is required for X12

syntax. Select the code that corresponds to the

organization that is responsible for the assignment

of the DoDAAC used to construct the controlling

document number for the transaction.

M ID 2/2 Must use

Code Name

DF Department of Defense (DoD)

DLMS Note:

Use to indicate that the Component is a Department of Defense agency, including Defense Logistics

Agency. Refer to ADC 1043.

DN Department of the Navy

DLMS Note:

Includes the United States Marine Corps.

DY Department of Air Force

DZ Department of Army

FG Federal Government

FA102 1300 Service, Promotion, Allowance, or Charge Code

Description: Code identifying the service,

promotion, allowance, or charge

O ID 4/4 Must use

Code Name

A170 Adjustments

DLMS Note:

Use only for adjustments not specified by any other code.

A520 Base Charge

DLMS Note:

Use for materiel charges only.

C930 Export Shipping Charge

D340 Goods and Services Charge

F060 Other Accessorial Service Charge

F560 Premium Transportation

I260 Transportation Direct Billing

DLMS Note:

Use for non-premium transportation.

R060 Packing, Crating, and Handling Charge
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 64 March 29, 2024

FA2 Accounting Data Pos: 286 Max: >1

Detail - Mandatory

Loop: FA1 Elements: 2

User Option (Usage): Must use

Purpose: To specify the detailed accounting data

DLMS Note:

1. Use this 2/FA2/286 segment to identify the various components of the line of accounting.

2. Use this segment to identify G-Invoicing 7600EZ Federal Intragovernmental Data Standards (FIDS) data elements.

3. Use this segment to comply with the DoD SLOA/Accounting Classification. Cost object elements Project Identifier, Funding Center

Identifier, Functional Area, Cost Element Code, Cost Center Identifier, Activity Identifier, and Work Order Number are used as appropriate

for the system.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

FA201 1196 Breakdown Structure Detail Code

Description: Codes identifying details relating to a

reporting breakdown structure tree

M ID 2/2 Must use

Code Name

18 Funds Appropriation

DLMS Note:

Use to indicate the basic appropriation number.

89 Budget Line Item Identification

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify, or to modify, “Budget Line Item”.

2. Qualifier 89 is a migration code approved for use in X12 version 4020. Refer to ADC 1043.

3. Authorized DLMS enhancement; see introductory DLMS note 3g.

90 Project/Task

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify, or to modify, “Project Identifier”. Refer to

ADC 1043.

2. Qualifier 90 is a migration code approved for use in X12 version 4020. 

3. Authorized DLMS enhancement; see introductory DLMS note 3g.

A1 Department Indicator

DLMS Note:

1. Use to identify the Requesting Agency Component TAS AID (Agency Identifier) in G-Invoicing related

transactions. Refer to ADC 1465.

2. For DoD SLOA/Accounting Classification use to identify, or to modify, “Department Regular”. Refer to

ADC 1043.

3. Authorized DLMS enhancement; see introductory DLMS note 3g.

A2 Transfer from Department

DLMS Note:

1. Use to identify the Requesting Agency Component TAS ATA (Allocation Transfer Agency Identifier)

in G-Invoicing related transactions. Refer to ADC 1465.

2. For DoD SLOA/Accounting Classification use to identify, or to modify, “Department Transfer”. Refer

to ADC 1043.

3. Authorized DLMS enhancement; see introductory DLMS note 3g.
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Code Name

004010F511M5MA56 65 March 29, 2024

A4 Basic Symbol Number

DLMS Note:

1. Use to identify the Requesting Agency Component TAS Main (Main Account Code) in G-Invoicing

related transactions. Refer to ADC 1465.

2. For DoD SLOA/Accounting Classification use to identify, or to modify, “Main Account”. Refer to ADC

1043.

3. Authorized DLMS enhancement; see introductory DLMS note 3g.

A5 Sub-class

DLMS Note:

1. Use to identify the Requesting Agency Component TAS SP (Sub- Level Prefix Code) in G-Invoicing

related transactions. Refer to ADC 1465.

2. Reserved for DoD SLOA/Accounting Classification use to identify, or to modify, “Sub Class”. Refer to

ADC 1043.

3. Sub Class is a potential future DLMS enhancement; see introductory DLMS note 3a.

A6 Sub-Account Symbol

DLMS Note:

1. Use to identify the Requesting Agency Component TAS SUB (Sub- Account Code) in G-Invoicing

related transactions. Refer to ADC 1465.

2. For DoD SLOA/Accounting Classification use to identify, or to modify, “Sub Account”. Refer to ADC

1043.

3. Authorized DLMS enhancement; see introductory DLMS note 3g.

AI Activity Identifier

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify, or to modify, “Activity Identifier”. Refer to

ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 3g.

3. Qualifier AI is a migration code approved for use in X12 version 7020.

B2 Budget Sub-activity Number

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify, or to modify, “Sub-Allocation (formerly

known as Limit/Subhead)”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 3g.

B5 Fund Code

DLMS Note:

Use to modify, or in the case of an unmatched modification, to identify the fund code. Modifier

transactions may not be used to change this field for GFM requisitions.

BE Business Event Type Code

DLMS Note:

1. Use to identify the Business Event Type Code (BETC) in G-Invoicing related transactions. Refer to

ADC 1465.

2. For DoD SLOA/Accounting Classification use to identify, or to modify, “Business Event Type Code”.

Refer to ADC 1043.

3. Authorized DLMS enhancement; see introductory DLMS note 3g.

4. Qualifier BE is a migration code approved for use in X12 version 7020.

1. Use to identify the Business Event Type Code (BETC) in G-Invoicing related transactions. Refer to

ADC 1465.

2. For DoD SLOA/Accounting Classification use to identify, or to modify, “Business Event Type Code”.

Refer to ADC 1043.

3. Authorized DLMS enhancement; see introductory DLMS note 3g.

4. Qualifier BE is a migration code approved for use in X12 version 7020.

C3 Budget Restriction

DLMS Note:

1. Use to identify the Requesting Agency Component TAS A (Availability Type Code) in G-Invoicing 
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Code Name

004010F511M5MA56 66 March 29, 2024

related transactions. Refer to ADC 1465.

2. For DoD SLOA/Accounting Classification use to identify, or to modify, “Availability Type”. Refer to

ADC 1043.

3. Authorized DLMS enhancement; see introductory DLMS note 3g.

CC Cost Center Identifier

DLMS Note:

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. Qualifier CC is a migration code approved for use in X12 version 7020.

F1 Object Class

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify, or to modify, “Object Class”. Refer to ADC

1043.

2. Authorized DLMS enhancement; see introductory DLMS note 3g.

FA Functional Area

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify, or to modify, “Functional Area”. Refer to

ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 3g.

3. Qualifier FA is a migration code approved for use in X12 version 7020.

FC Funding Center Identifier

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify, or to modify, “Funding Center Identifier”. 

Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 3g.

3. Qualifier FC is a migration code approved for use in X12 version 7020.

FT Funding Type

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify, or to modify, “Reimbursable Flag”. Refer to

ADC 1043. 

2. Qualifier FT is an X12 Version Release 004030 Migration Code. 

3. Authorized DLMS enhancement; see introductory DLMS note 3g.

H1 Cost Code

DLMS Note:

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.

IA Security Cooperation Implementing Agency

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Security Cooperation Implementing

Agency”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 3g.

3. Qualifier IA is a migration code approved for use in X12 version 7020.

L1 Accounting Installation Number
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Code Name

004010F511M5MA56 67 March 29, 2024

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify, or to modify, “Agency Accounting Identifier”. 

Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory DLMS note 3g.

P1 Disbursing Station Number

DLMS Note:

1. Use to identify the Agency Location Code (ALC) in G-Invoicing related transactions. Refer to ADC

1465.

2. For DoD SLOA/Accounting Classification use to identify, or to modify, “Agency Dispersing Identifier

Code”. Refer to ADC 1043.

3. Authorized DLMS enhancement; see introductory DLMS note 3g.

P5 Foreign Military Sales (FMS) Line Item Number

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Security Cooperation Case Line Item

Identifier”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 3g.

S1 Security Cooperation Customer Code

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Security Cooperation Customer Code”. 

Refer to ADC 1043.

2. DLMS enhancement; see introductory DLMS note 3d. A field size exceeding 2 positions is not

supportable under current MILSTRIP and MAPAC processes. Three character codes are not

authorized at this time.

3. Qualifier S1 is a migration code approved for use in X12 version 7020.

1. For DoD SLOA/Accounting Classification use to identify “Security Cooperation Customer Code”. 

Refer to ADC 1043.

2. DLMS enhancement; see introductory DLMS note 3d. A field size exceeding 2 positions is not

supportable under current MILSTRIP and MAPAC processes. Three character codes are not

authorized at this time.

3. Qualifier S1 is a migration code approved for use in X12 version 7020.

S2 Security Cooperation Case Designator

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Security Cooperation Case Designator”. 

Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 3g. A field size exceeding 3 positions

is not supportable under current MILSTRIP processes. Four character codes are not authorized at this

time.

3. Qualifier S2 is a migration code approved for use in X12 version 7020.

1. For DoD SLOA/Accounting Classification use to identify “Security Cooperation Case Designator”. 

Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 3g. A field size exceeding 3 positions

is not supportable under current MILSTRIP processes. Four character codes are not authorized at this

time.

3. Qualifier S2 is a migration code approved for use in X12 version 7020.

WO Work Order Number

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify, or to modify, “Work Order Number”. Refer

to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 3g.

3. Qualifier WO is a migration code approved for use in X12 version 7020.

YB Beginning Period of Availability

DLMS Note:

1. Use to identify the Requesting Agency Component TAS BPOA (Beginning Period of Availability) in

G-Invoicing related transactions. Refer to ADC 1465.

2. For DoD SLOA/Accounting Classification use to identify, or to modify, “Beginning Period of

Availability Fiscal Year Date”. Refer to ADC 1043.

3. Use as appropriate to represent Program Year. Availability Type Code must be “X”. Refer to ADC

1043B.

4. Authorized DLMS enhancement; see introductory DLMS note 3g.

1. Use to identify the Requesting Agency Component TAS BPOA (Beginning Period of Availability) in

G-Invoicing related transactions. Refer to ADC 1465.

2. For DoD SLOA/Accounting Classification use to identify, or to modify, “Beginning Period of

Availability Fiscal Year Date”. Refer to ADC 1043.

3. Use as appropriate to represent Program Year. Availability Type Code must be “X”. Refer to ADC

1043B.

4. Authorized DLMS enhancement; see introductory DLMS note 3g.
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

Code Name

004010F511M5MA56 68 March 29, 2024

5. Qualifier YB is a migration code approved for use in X12 version 7020.

YE Ending Period of Availability

DLMS Note:

1. Use to identify the Requesting Agency Component TAS EPOA (Ending Period of Availability) in

G-Invoicing related transactions. Refer to ADC 1465.

2. For DoD SLOA/Accounting Classification use to identify, or to modify, “Ending Period of Availability

Fiscal Year Date”. Refer to ADC 1043.

3. Authorized DLMS enhancement; see introductory DLMS note 3g.

4. Qualifier YE is a migration code approved for use in X12 version 7020.

1. Use to identify the Requesting Agency Component TAS EPOA (Ending Period of Availability) in

G-Invoicing related transactions. Refer to ADC 1465.

2. For DoD SLOA/Accounting Classification use to identify, or to modify, “Ending Period of Availability

Fiscal Year Date”. Refer to ADC 1043.

3. Authorized DLMS enhancement; see introductory DLMS note 3g.

4. Qualifier YE is a migration code approved for use in X12 version 7020.

FA202 1195 Financial Information Code

Description: Code representing financial

accounting information

M AN 1/80 Must use
DLMS Implementation Convention (IC) 511M -

Requisition Modification

ADC 59, 69A, 75, 76, 77, 97, 169, 186, 221, 221A, 243, 263, 264, 274, 276, 284, 284A, 322, 328, 352, 359,

375, 377, 381, 381B, 435, 436, 448, 448B, 466, 473, 473A, 1009A, 1014, 1014A, 1020, 1023, 1043, 1043A,

1043B, 1043C, 1050, 1068, 1075, 1110, 1123, 1136, 1161, 1176, 1184, 1287, 1306, 1307, 1307A, 1321,

1343, 1360, 1367, 1370, 1381, 1390, 1412, 1420, 1454 and 1465 DLM 4000.25

004010F511M5MA56 69 March 29, 2024

SE Transaction Set Trailer Pos: 290 Max: 1

Detail - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must use

Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending

(SE) segments)

Comments: 

1. SE is the last segment of each transaction set.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

SE01 96 Number of Included Segments

Description: Total number of segments included in

a transaction set including ST and SE segments

M N0 1/10 Must use

SE02 329 Transaction Set Control Number

Description: Identifying control number that must

be unique within the transaction set functional group

assigned by the originator for a transaction set

DLMS Note: Cite the same number as the one cited

in ST02.

M AN 4/9 Must use