DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

004010F867I5IA43 1 February 13, 2024

867 Product Transfer and Resale Report

Functional Group=PT

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Product Transfer and Resale Report

Transaction Set (867) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to: (1)

report information about product that has been transferred from one location to another; (2) report sales of product from one or more locations

to an end customer; or (3) report sales of a product from one or more locations to an end customer, and demand beyond actual sales (lost

orders). Report may be issued by either buyer or seller.

DLMS Note:

1. Storage organizations use this transaction set to report materiel issues to Inventory Control Points (ICPs) or Integrated Materiel Managers

(IMMs). This transaction encompasses functionality of MILSTRAP Document Identifier Code (DIC) D7_. This transaction also

accommodates the functionality of non-DLSS DIC BG1/BG2 serial/lot number reporting transactions (published by NAVSUP P-724).

2. Use a single occurrence of this transaction set to exchange transactions between a single storage organization and a single or multiple

ICPs or IMMs. DoD logistics users should refer to the Defense Logistics Management Standards (DLMS) Implementation Convention (IC)

available at URL: http://www.dla.mil/HQ/InformationOperations/DLMS/elibrary/Transformats/140_997/#867. The DLMS IC provides specific

business rules, conditions, and authorized codes necessary for appropriate use of the IC within the DLMS.

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

Conversion Table which can be found on the Defense Enterprise Data Standards Office (DEDSO) Web site at www.dla.mil/does/DLMS

4. DLSS functionality allows for Service or Agency data in various RP(s). Data conveyed therein will require Service or Agency identification

to DEDSO and incorporation into the DLMS.

5. This DLMS Implementation Convention (IC) 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. Defense Logistics Standard System (DLSS) data which must be retained in the DLMS for a transition period to support transaction

conversion in a mixed DLSS/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 files size above existing DLSS capability which may not be supported by the recipient's

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

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

f. Data required to accommodate Component-unique transaction requirements (e.g, C-series transactions). Data does not apply to DLSS

transactions.

g. Repetition of data (using multiple iterations or loops) which is not compatible with existing DLSS capability. Although supported by the use

of the ANSI X12 standard, such data is not compatible with DLSS/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.

6. This transaction may be used to provide item unique identification (IUID) information only on a limited scope. Loop ID LX (2/LX/280)

documents the authorized uses of unique item identifier (UII) and serial number. For all other purposes, the UII/serial number information is

a placeholder for DLMS enhancements pending development of DLMS procedures and overarching OSD Supply Policy. Refer to the item

unique identification (IUID) web at URL: http://www.acq.osd.mil/dpap/pdi/uid/ for DoD policy.

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

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

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

- ADC 153, Inclusion of Data Supporting Unique Identification (UID) of Items in DLMS Supplement 867I, Product Transfer and Resale

Report (Issue), and Administrative Changes (Supply)

- ADC 165, Optional Capability for Sending Information Copy of DLMS Supplements 856, 856S, 861, 867I, 870M, 945A, to a Component

Unique Item Tracking (UIT) Registry (Supply)

- ADC 197, Request for New Type of Physical Inventory/Transaction History Code and Add Code to Historical Transactions (DS 527R, 867I,

940R, 945A)

1. Storage organizations use this transaction set to report materiel issues to Inventory Control Points (ICPs) or Integrated Materiel Managers

(IMMs). This transaction encompasses functionality of MILSTRAP Document Identifier Code (DIC) D7_. This transaction also

accommodates the functionality of non-DLSS DIC BG1/BG2 serial/lot number reporting transactions (published by NAVSUP P-724).

2. Use a single occurrence of this transaction set to exchange transactions between a single storage organization and a single or multiple

ICPs or IMMs. DoD logistics users should refer to the Defense Logistics Management Standards (DLMS) Implementation Convention (IC)

available at URL: http://www.dla.mil/HQ/InformationOperations/DLMS/elibrary/Transformats/140_997/#867. The DLMS IC provides specific

business rules, conditions, and authorized codes necessary for appropriate use of the IC within the DLMS.

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

Conversion Table which can be found on the Defense Enterprise Data Standards Office (DEDSO) Web site at www.dla.mil/does/DLMS

4. DLSS functionality allows for Service or Agency data in various RP(s). Data conveyed therein will require Service or Agency identification

to DEDSO and incorporation into the DLMS.

5. This DLMS Implementation Convention (IC) 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. Defense Logistics Standard System (DLSS) data which must be retained in the DLMS for a transition period to support transaction

conversion in a mixed DLSS/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 files size above existing DLSS capability which may not be supported by the recipient's

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

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

f. Data required to accommodate Component-unique transaction requirements (e.g, C-series transactions). Data does not apply to DLSS

transactions.

g. Repetition of data (using multiple iterations or loops) which is not compatible with existing DLSS capability. Although supported by the use

of the ANSI X12 standard, such data is not compatible with DLSS/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.

6. This transaction may be used to provide item unique identification (IUID) information only on a limited scope. Loop ID LX (2/LX/280)

documents the authorized uses of unique item identifier (UII) and serial number. For all other purposes, the UII/serial number information is

a placeholder for DLMS enhancements pending development of DLMS procedures and overarching OSD Supply Policy. Refer to the item

unique identification (IUID) web at URL: http://www.acq.osd.mil/dpap/pdi/uid/ for DoD policy.

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

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

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

- ADC 153, Inclusion of Data Supporting Unique Identification (UID) of Items in DLMS Supplement 867I, Product Transfer and Resale

Report (Issue), and Administrative Changes (Supply)

- ADC 165, Optional Capability for Sending Information Copy of DLMS Supplements 856, 856S, 861, 867I, 870M, 945A, to a Component

Unique Item Tracking (UIT) Registry (Supply)

- ADC 197, Request for New Type of Physical Inventory/Transaction History Code and Add Code to Historical Transactions (DS 527R, 867I,

940R, 945A)
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

004010F867I5IA43 2 February 13, 2024

- ADC 201, Revisions to DLMS Supplement 867I to Support Requirements for the Army Medical Material Agreement Issue Transactions

- ADC 235, Revise DLMS Supplement (DS) 867I and MILSTRAP Issue Transactions to Support Navy Issue On Request Code and

Administrative DS 867I Updates

- ADC 259, Revise DS 867I and MILSTRAP Issue Transactions to Support Navy Issue Reversal Code (Supply) 

- ADC 261, Migrate Navy Serial Number and Lot Number Transactions (NAVSUP P-724 BG1/BG2) to DLMS 527R Receipt, 867I Issue, and

947I Inventory Adjustment

- ADC 271, Revisions to DLMS Supplement 867I Issue to Add Build Directive Number (BDN) to Support the Theater Enterprise-Wide

Logistics System (TEWLS) and DS 867I Administrative Updates

- ADC 295, Use of DLMS Qualifier for Local Stock Number/Management Control Numbers

- ADC 341, Revise DLMS Supplement (DS) 867I Issue in Support of Navy Enterprise Resource Program (ERP) and Commercial Asset

Visibility II (CAV II) Systems with Interim Measure for CAV Detail Issue Transaction (Supply)

- ADC 347, Revise DLMS Supplement (DS) 527R Receipt, 867I Issue, 945A Materiel Release Advice, and 947I Inventory Adjustment to

Support Unique Item Tracking for Air Force Positive Inventory Control (PIC)

- Withdrawal of Approved MILSTRAP/MILSTRIP Change Letter (AMCL) 5 and 13, Date Packed/Expiration for Subsistence Items (Staffed by

PMCLs 3) (Supply/MILSTRIP/MILSTRAP)

- ADC 373, Document Process for Material Control Tracking (MCT) Tag Number and Revise DLMS 527D, 527R, 940R, and 945A in Support

of BRAC SS&D/IMSP (Supply)

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

BRAC SS&D/IMSP

- Approved Addendum ADC 381A, Procedures and Additional Data Content supporting Unit of Use Requirements under Marine Corps

BRAC Storage and Distribution

- ADC 409, Intra-DLA Revisions to DLMS 867I Issue and Associated Procedures to Support Relocation of Material between DLA Disposition

Services Field Offices under Reutilization Business Integration (RBI) (Supply)

- ADC 435, DLMS Revisions for 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 Routing Identifiers

- ADC 445, Adopt Navy Serial Number and Lot Number Transactions (NAVSUP P-724 BG1/BG2) to Air Force and Marine Corps

Ammunition System Use for DLMS 527R Receipt, 846R Location Reconciliation Request, 867I Issue, and 947I Inventory Adjustment

(Supply)

- ADC 461, Revision for Commercial Asset Visibility-Organic Repairables Module (CAV-ORM) Estimated Completion Date (ECD) field on the

MILSTRAP DAC and DLMS 947I ECD transaction , and Administrative Update to 527D, 527R, 867I , 856S (Supply/MILSTRAP/MILSTRIP)

- 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 1020, Inter-Service Ownership Transfer of Ammunition/ Ammunition Related Materiel

- 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

- Organizational Name and Other Non-Substantive (Administrative) Updates Completed on August 25, 2014. 

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

- ADC 1160, Procedures for Recommending and Authorizing Credit for Validated SDRs, Associated Reply Code Revisions, and Required

use of the Reason for Reversal Code in Issue Reversals

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

Conventions and DLMS Manuals

- ADC 1198A, Establishing and Maintaining Accountability for Service Owned Capital Equipment Stored at DLA Distribution Centers –

(Missing Serial Numbers, and Remove 867I Issue Transaction)

- ADC 1207, Intra-DLA Revisions to DLMS 945A and Associated Procedures to Support Relocation of Material between DLA Disposition

Services Field Offices

- Administrative Update to Reflect Realignment to Recognize DLMS Program Office Completed on November 28, 2016

- ADC 1224, Requirements for Air Force Government Furnished Property (GFP) Accountability including Identification of the Contractor

Inventory Control Point (CICP), the Physical Location of Property, the Authorizing Procurement Instrument Identifier (PIID), Disposal

Information in the Issue Transaction, and Enhanced Data Content in Inventory-Related Transactions

- ADC 1224A, Requirements for Air Force Government Furnished Property (GFP) Accountability including Identification of the Contractor

Inventory Control Point (CICP), the Physical Location of Property, the Authorizing Procurement Instrument Identifier (PIID), Disposal

Information in the Issue Transaction, and Enhanced Data Content in Inventory-Related Transactions

- ADC 1230A, Approved Addendum to include the DLMS 867I Issue Transaction and Associated Procedures for Air Force Government

Furnished Property Accountability (GFP-A) (Supply/Finance)

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

September 28, 2018

- 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 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 1383 Deletion of Unused Qualifier Related to Transportation/Method Codes

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

Office (DEDSO) - Completed on March 10, 2022

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

Indicator to Wide Area Workflow

- ADC 201, Revisions to DLMS Supplement 867I to Support Requirements for the Army Medical Material Agreement Issue Transactions

- ADC 235, Revise DLMS Supplement (DS) 867I and MILSTRAP Issue Transactions to Support Navy Issue On Request Code and

Administrative DS 867I Updates

- ADC 259, Revise DS 867I and MILSTRAP Issue Transactions to Support Navy Issue Reversal Code (Supply) 

- ADC 261, Migrate Navy Serial Number and Lot Number Transactions (NAVSUP P-724 BG1/BG2) to DLMS 527R Receipt, 867I Issue, and

947I Inventory Adjustment

- ADC 271, Revisions to DLMS Supplement 867I Issue to Add Build Directive Number (BDN) to Support the Theater Enterprise-Wide

Logistics System (TEWLS) and DS 867I Administrative Updates

- ADC 295, Use of DLMS Qualifier for Local Stock Number/Management Control Numbers

- ADC 341, Revise DLMS Supplement (DS) 867I Issue in Support of Navy Enterprise Resource Program (ERP) and Commercial Asset

Visibility II (CAV II) Systems with Interim Measure for CAV Detail Issue Transaction (Supply)

- ADC 347, Revise DLMS Supplement (DS) 527R Receipt, 867I Issue, 945A Materiel Release Advice, and 947I Inventory Adjustment to

Support Unique Item Tracking for Air Force Positive Inventory Control (PIC)

- Withdrawal of Approved MILSTRAP/MILSTRIP Change Letter (AMCL) 5 and 13, Date Packed/Expiration for Subsistence Items (Staffed by

PMCLs 3) (Supply/MILSTRIP/MILSTRAP)

- ADC 373, Document Process for Material Control Tracking (MCT) Tag Number and Revise DLMS 527D, 527R, 940R, and 945A in Support

of BRAC SS&D/IMSP (Supply)

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

BRAC SS&D/IMSP

- Approved Addendum ADC 381A, Procedures and Additional Data Content supporting Unit of Use Requirements under Marine Corps

BRAC Storage and Distribution

- ADC 409, Intra-DLA Revisions to DLMS 867I Issue and Associated Procedures to Support Relocation of Material between DLA Disposition

Services Field Offices under Reutilization Business Integration (RBI) (Supply)

- ADC 435, DLMS Revisions for 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 Routing Identifiers

- ADC 445, Adopt Navy Serial Number and Lot Number Transactions (NAVSUP P-724 BG1/BG2) to Air Force and Marine Corps

Ammunition System Use for DLMS 527R Receipt, 846R Location Reconciliation Request, 867I Issue, and 947I Inventory Adjustment

(Supply)

- ADC 461, Revision for Commercial Asset Visibility-Organic Repairables Module (CAV-ORM) Estimated Completion Date (ECD) field on the

MILSTRAP DAC and DLMS 947I ECD transaction , and Administrative Update to 527D, 527R, 867I , 856S (Supply/MILSTRAP/MILSTRIP)

- 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 1020, Inter-Service Ownership Transfer of Ammunition/ Ammunition Related Materiel

- 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

- Organizational Name and Other Non-Substantive (Administrative) Updates Completed on August 25, 2014. 

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

- ADC 1160, Procedures for Recommending and Authorizing Credit for Validated SDRs, Associated Reply Code Revisions, and Required

use of the Reason for Reversal Code in Issue Reversals

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

Conventions and DLMS Manuals

- ADC 1198A, Establishing and Maintaining Accountability for Service Owned Capital Equipment Stored at DLA Distribution Centers –

(Missing Serial Numbers, and Remove 867I Issue Transaction)

- ADC 1207, Intra-DLA Revisions to DLMS 945A and Associated Procedures to Support Relocation of Material between DLA Disposition

Services Field Offices

- Administrative Update to Reflect Realignment to Recognize DLMS Program Office Completed on November 28, 2016

- ADC 1224, Requirements for Air Force Government Furnished Property (GFP) Accountability including Identification of the Contractor

Inventory Control Point (CICP), the Physical Location of Property, the Authorizing Procurement Instrument Identifier (PIID), Disposal

Information in the Issue Transaction, and Enhanced Data Content in Inventory-Related Transactions

- ADC 1224A, Requirements for Air Force Government Furnished Property (GFP) Accountability including Identification of the Contractor

Inventory Control Point (CICP), the Physical Location of Property, the Authorizing Procurement Instrument Identifier (PIID), Disposal

Information in the Issue Transaction, and Enhanced Data Content in Inventory-Related Transactions

- ADC 1230A, Approved Addendum to include the DLMS 867I Issue Transaction and Associated Procedures for Air Force Government

Furnished Property Accountability (GFP-A) (Supply/Finance)

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

September 28, 2018

- 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 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 1383 Deletion of Unused Qualifier Related to Transportation/Method Codes

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

Office (DEDSO) - Completed on March 10, 2022

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

Indicator to Wide Area Workflow
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

004010F867I5IA43 3 February 13, 2024

- 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 1464, Segregation of Materiel Below Line Item (Inventory Management)

Heading:

Pos Id Segment Name Req Max Use Repeat Notes Usage

10 ST Transaction Set Header M 1 Must use

20 BPT Beginning Segment for Product

Transfer and Resale

M 1 Must use

* 40 CUR Currency O 1 Not Used

* 50 DTM Date/Time Reference O 10 Not Used

* 60 REF Reference Identification O 12 Not Used

* 70 PER Administrative Communications

Contact

O 3 Not Used

* 75 MEA Measurements O 20 Not Used

* 78 PSA Partner Share Accounting O 10 Not Used

LOOP ID - N1 LOOP ID - N1 5

80 N1 Name O 1 Must use

* 90 N2 Additional Name Information O 2 Not Used

* 100 N3 Address Information O 2 Not Used

* 110 N4 Geographic Location O 1 Not Used

* 120 REF Reference Identification O 12 Not Used

* LOOP ID - PER * LOOP ID - PER >1

* 130 PER Administrative Communications

Contact

O 1 Not Used

* 135 REF Reference Identification O >1 Not Used

* LOOP ID - LM * LOOP ID - LM >1

* 140 LM Code Source Information O 1 Not Used

* 150 LQ Industry Code M 100 Not Used

Detail:

Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - PTD LOOP ID - PTD >1

10 PTD Product Transfer and Resale

Detail

M 1 Must use

20 DTM Date/Time Reference O 10 Must use

30 REF Reference Identification O 20 Must use

* 35 PRF Purchase Order Reference O 1 Not Used

* 40 PER Administrative Communications

Contact

O 3 Not Used

* 45 MAN Marks and Numbers O 1 Not Used

LOOP ID - N1 LOOP ID - N1 5

50 N1 Name O 1 Used

* 60 N2 Additional Name Information O 2 Not Used

* 70 N3 Address Information O 2 Not Used

* 80 N4 Geographic Location O 1 Not Used

* 90 REF Reference Identification O 20 Not Used

* 100 PER Administrative Communications

Contact

O 3 Not Used

* LOOP ID - SII * LOOP ID - SII >1

* 105 SII Sales Item Information O 1 Not Used

* 107 N9 Reference Identification O 1 Not Used

LOOP ID - QTY LOOP ID - QTY >1
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

Pos Id Segment Name Req Max Use Repeat Notes Usage

004010F867I5IA43 4 February 13, 2024

110 QTY Quantity O 1 Must use

* 120 LIN Item Identification O 1 Not Used

* 122 PO3 Additional Item Detail O 25 Not Used

* 125 PO4 Item Physical Details O 1 Not Used

* 130 UIT Unit Detail O 12 Not Used

140 AMT Monetary Amount O 12 Used

* 141 ITA Allowance, Charge or Service O 10 Not Used

* 150 PID Product/Item Description O 200 Not Used

160 MEA Measurements O 40 Used

* 170 PWK Paperwork O 25 Not Used

* 180 PKG Marking, Packaging, Loading O 25 Not Used

* 190 REF Reference Identification O >1 Not Used

* 200 PER Administrative Communications

Contact

O 3 Not Used

* 210 DTM Date/Time Reference O 10 Not Used

* 220 CUR Currency O 1 Not Used

240 DD Demand Detail O 1 Used

* 250 LDT Lead Time O 1 Not Used

LOOP ID - LM LOOP ID - LM >1

260 LM Code Source Information O 1 Must use

270 LQ Industry Code O 100 Must use

LOOP ID - LX LOOP ID - LX >1 N2/280L N2/280L

280 LX Assigned Number O 1 N2/280 Used

290 REF Reference Identification O >1 Used

300 DTM Date/Time Reference O 1 Used

310 N1 Name O 1 Used

* LOOP ID - LM * LOOP ID - LM >1

* 320 LM Code Source Information O 1 Not Used

* 330 LQ Industry Code M 100 Not Used

LOOP ID - FA1 LOOP ID - FA1 >1

340 FA1 Type of Financial Accounting

Data

O 1 Used

350 FA2 Accounting Data M >1 Must use

Summary:

Pos Id Segment Name Req Max Use Repeat Notes Usage

* LOOP ID - CTT * LOOP ID - CTT 1 N3/10L

* 10 CTT Transaction Totals O 1 N3/10 Not Used

* 20 AMT Monetary Amount O 12 Not Used

* 21 ITA Allowance, Charge or Service O 10 Not Used

30 SE Transaction Set Trailer M 1 Must use

Notes: 

2/280L The LX loop conveys serial number, lot number, and inventory data.

2/280 The LX loop conveys serial number, lot number, and inventory data.

3/10L The number of line items (CTT01) is the accumulation of the number of LIN segments. If used, hash total (CTT02) is the sum of the

value of quantities (QTY02) for each QTY segment.

3/10 The number of line items (CTT01) is the accumulation of the number of LIN segments. If used, hash total (CTT02) is the sum of the

value of quantities (QTY02) for each QTY segment.
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

004010F867I5IA43 5 February 13, 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 Rep

ST01 143 Transaction Set Identifier Code

Description: Code uniquely identifying a

Transaction Set

M ID 3/3 Must use 1

Code Name

867 Product Transfer and Resale Report

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 1
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

004010F867I5IA43 6 February 13, 2024

BPT Beginning Segment for Product

Transfer and Resale

Pos: 20 Max: 1

Heading - Mandatory

Loop: N/A Elements: 5

User Option (Usage): Must use

Purpose: To indicate the beginning of the Product Transfer and Resale Report Transaction Set and transmit identifying data

Syntax Rules: 

1. P0506 - If either BPT05 or BPT06 is present, then the other is required.

Semantics: 

1. BPT02 identifies the transfer/resale number.

2. BPT03 identifies the transfer/resale date.

3. BPT08 identifies the transfer/resale time.

4. BPT09 is used when it is necessary to reference a Previous Report Number.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

BPT01 353 Transaction Set Purpose Code

Description: Code identifying purpose of

transaction set

M ID 2/2 Must use 1

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 are not processed 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.

BPT03 373 Date

Description: Date expressed as

CCYYMMDD

DLMS Note: 1. Use to identify the date of

transaction set preparation. This date

corresponds to the Universal Time

Coordinate (UTC).

2. Authorized DLMS enhancement; see

introductory DLMS note 5e.

M DT 8/8 Must use 1

BPT04 755 Report Type Code

Description: Code indicating the title or

contents of a document, report or

supporting item

O ID 2/2 Must use 1

Code Name

01 Product Transfer

DLMS Note:

Use to identify issue transactions. (MILSTRAP DIC D7_functionality.)
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

004010F867I5IA43 7 February 13, 2024

BPT07 306 Action Code

Description: Code indicating type of action

O ID 1/2 Used 1

Code Name

FI File

DLMS Note:

Authorized for Air Force and DSS use with PIC NWRM UIT. Use to identify an issue image transaction

where the original issue transaction has bypassed the normal DAAS transaction flow. All transaction set

recipients must use extreme caution to ensure that individual transactions with this code do not process

as action documents which affect accountable records. Must use with 2/N101/50 code ‘KK’ and

2/N106/50 code ‘PK’. There will be no 2/N106/50 code ‘TO’ for this transaction. Refer to ADC 347.

W1 Reconcile Historical Records

DLMS Note:

Use to indicate the submission of historical information on previously reported issues. Recipients may

not reject these transactions.

BPT08 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 (00-99)

DLMS Note: 1. Use to identify the

originator's time of transaction set

preparation in UTC.

2. Express time in a four-position (HHMM)

format. 

3. Authorized DLMS enhancement; see

introductory DLMS note 5e.

O TM 4/8 Used 1
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

004010F867I5IA43 8 February 13, 2024

N1 Name Pos: 80 Max: 1

Heading - Optional

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/080 loop to identify the organization originating the transaction set.

2. Use additional iterations to identify other organizations associated with the transaction.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N101 98 Entity Identifier Code

Description: Code identifying an

organizational entity, a physical location,

property or an individual

DLMS Note: For DLMS use, only the

following codes are authorized.

M ID 2/3 Must use 1

Code Name

BT Bill-to-Party

DLMS Note:

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

2. Authorized DLMS enhancement; see introductory DLMS note 5e.

SB Storage Area

DLMS Note:

1. Use to identify the depot or storage activity. Use the Routing Identifier Code (RIC) for the activity

unless otherwise authorized.

2. For Air Force GFP accountability, use to identify the CICP as the responsible custodial activity. 

Refer to ADC 1224.

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.

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 1
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

004010F867I5IA43 9 February 13, 2024

Code Name

10 Department of Defense Activity Address Code (DODAAC)

DLMS Note:

DLMS enhancement; see introductory DLMS note 5a.

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 5e.

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.

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 1

N106 98 Entity Identifier Code

Description: Code identifying an

organizational entity, a physical location,

property or an individual

O ID 2/3 Used 1

Code Name

FR Message From

DLMS Note:

Must use to indicate the organization cited in N104 is originating the transaction set.
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

004010F867I5IA43 10 February 13, 2024

PTD Product Transfer and Resale Detail Pos: 10 Max: 1

Detail - Mandatory

Loop: PTD Elements: 1

User Option (Usage): Must use

Purpose: To indicate the start of detail information relating to the transfer/resale of a product and provide identifying data

Syntax Rules: 

1. P0203 - If either PTD02 or PTD03 is present, then the other is required.

2. P0405 - If either PTD04 or PTD05 is present, then the other is required.

DLMS Note:

Use to indicate the specific type of issue being reported.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

PTD01 521 Product Transfer Type Code

Description: Code identifying the type of

product transfer

DLMS Note: 1. The information conveyed

by this code corresponds to the information

conveyed by the third position of

MILSTRAP DIC D7_. The corresponding

MILSTRAP DIC is shown after each

Product Transfer Type Code below for

information in a mixed DLSS/DLMS

environment.

DLMS Note: 1. The information conveyed

by this code corresponds to the information

conveyed by the third position of

MILSTRAP DIC D7_. The corresponding

MILSTRAP DIC is shown after each

Product Transfer Type Code below for

information in a mixed DLSS/DLMS

environment.

2. For DLMS use, only the following codes

are authorized.

M ID 2/2 Must use 1

Code Name

BC Issue - Other Agency

DLMS Note:

Issue (Non-DoD Activities) - Use to identify issues to non-DoD activities. Excludes issues of end items

to be repaired. (Corresponds to MILSTRAP DIC D7C.)

BD Issue - Other Department

DLMS Note:

Issue (DoD Activities) - Use to identify issues to other DoD activities. Excludes issues of end items to

be repaired. (Corresponds to MILSTRAP DIC D7B.)

BE Grant Aid

DLMS Note:

Issue (Grant Aid) - Use to identify issues to a Security Assistance (SA) (Grant Aid) program. 

(Corresponds to MILSTRAP DIC D7D.)

BF Foreign Military Sale

DLMS Note:

Issue (Foreign Military Sales) - Use to identify issues to a SA (Foreign Military Sales (FMS)) program. 

(Corresponds to MILSTRAP DIC D7E.)

BG Test and Evaluation

DLMS Note:

Issue (Destructive Test/Evaluation) Use to identify issues for destructive test and/or evaluation when

the item is not expected to be returned. (Corresponds to MILSTRAP DIC D7G.)

BH Furnished Goods and Services

DLMS Note:

Issue (Furnished Materiel for Consumption) - Issue of materiel furnished by the owner to be consumed

or expended in the manufacturing or maintenance process. Includes issues from inventory or by direct

delivery from a vendor. Excludes materiel furnished for incorporation in the deliverable item. 
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

Code Name

004010F867I5IA43 11 February 13, 2024

(Corresponds to MILSTRAP DIC D7H.)

BI Reutilization and Marketing

DLMS Note:

Issue (Reutilization and Marketing) - Use to identify issues to a Defense Reutilization and Marketing

Office (DRMO). (Corresponds to MILSTRAP DIC D7J.)

BJ Relocation

DLMS Note:

Issue (Relocation) - Use to identify issues for relocation between storage activities without change in

ownership. Excludes issues of items for repair or test/evaluation. (Corresponds to MILSTRAP DIC

D7K.)

BK Modification

DLMS Note:

Issue (Assembly/Disassembly/Reclamation/Conversion/Modification) - Use to identify issues of

components for assembly or items for disassembly, reclamation, conversion, or modification furnished

by the owner from inventory or by direct delivery from vendor. Includes materiel furnished for

incorporation in a deliverable item. Excludes issue of materiel furnished to be consumed or expended

during the manufacture or maintenance process. (Corresponds to MILSTRAP DIC D7L.)

BL Repair or Nondestructive Testing

DLMS Note:

Issue (Repair or Nondestructive Test/Evaluation) - Use to identify issues from inventory for repair or

nondestructive test/evaluation and expected return of the same item. (Corresponds to MILSTRAP DIC

D7M.)

BM Loan

DLMS Note:

Issue (Loan) - Use to identify issues from inventory for loan to authorized recipients. Includes

Government-owned equipment furnished for use in performing a contract. (Corresponds to MILSTRAP

DIC D7N.)

BN Return

DLMS Note:

Issue (Returned Purchases) - Use to identify issues of returned purchases from inventory to suppliers

for credit or reimbursement. (Corresponds to MILSTRAP DIC D7P.)

BO Designated Items

DLMS Note:

Issue (Designated Items) - Use to identify issues of designated items from inventory for installation on a

principal item/weapon system. (Corresponds to MILSTRAP DIC D7Q.)

BQ Other

DLMS Note:

Use to identify issues from inventory when a specific Product Transfer Type Code is not otherwise

provided. Assignor of code will maintain detailed intelligence pertaining to its use. (Corresponds to

MILSTRAP DIC D7Z.)

BR Exchange

DLMS Note:

Issue (Exchange Items) - Use to identify issues when a like item is returned on an exchange basis. 

(Corresponds to MILSTRAP DIC D7R.)

SM Sample

DLMS Note:

Used for CAV Detail Record. Authorized for INTERIM USE by Navy as a flag to identify CAV

non-balance affecting ‘detail’ issue transactions. The balance affecting CAV “summary” issue

transaction must use the appropriate standard product transfer type code. Code ‘SM’ is nonstandard

and is authorized for intra-Navy interim use pending implementation of “detail” information within a

standard DLMS issue transaction through looping structure. Navy will address CAV becoming

compliant with DLMS standard after Navy ERP completes the Single Supply Solution Release 1.1

implementation in 2012. PTD01 code ‘SM’ will be deleted from 867I at that time. Refer to ADC 341.

Used for CAV Detail Record. Authorized for INTERIM USE by Navy as a flag to identify CAV

non-balance affecting ‘detail’ issue transactions. The balance affecting CAV “summary” issue

transaction must use the appropriate standard product transfer type code. Code ‘SM’ is nonstandard

and is authorized for intra-Navy interim use pending implementation of “detail” information within a

standard DLMS issue transaction through looping structure. Navy will address CAV becoming

compliant with DLMS standard after Navy ERP completes the Single Supply Solution Release 1.1

implementation in 2012. PTD01 code ‘SM’ will be deleted from 867I at that time. Refer to ADC 341.

SS Stock Sale

DLMS Note:

Issue (Own Service/Agency) - Use to identify issues to own service or agency. Excludes issues of end 
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

Code Name

004010F867I5IA43 12 February 13, 2024

items to be repaired. (Corresponds to MILSTRAP DIC D7A.)
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

004010F867I5IA43 13 February 13, 2024

DTM Date/Time Reference Pos: 20 Max: 10

Detail - Optional

Loop: PTD Elements: 3

User Option (Usage): Must use

Purpose: To specify pertinent dates and times

Syntax Rules: 

1. R020305 - At least one of DTM02, DTM03 or DTM05 is required.

2. C0403 - If DTM04 is present, then DTM03 is required.

3. P0506 - If either DTM05 or DTM06 is present, then the other is required.

DLMS Note:

Must use this 2/DTM/020 to identify dates associated with the transaction.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

DTM01 374 Date/Time Qualifier

Description: Code specifying type of date

or time, or both date and time

DLMS Note: For DLMS use, only the

following codes are authorized.

M ID 3/3 Must use 1

Code Name

011 Shipped

DLMS Note:

1. Use with Commercial Asset Visibility (CAV) transactions to indicate date shipped.

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

102 Issue

DLMS Note:

1. Use to identify the materiel issue date (date materiel was dropped from the custodial

“available-for-issue” balance).

2. Authorized DLMS enhancement; see introductory DLMS note 5e. on IC cover page.

140 Actual

DLMS Note:

Use to identify date transaction was prepared.

938 Order

DLMS Note:

Use in commercial asset visibility (CAV) to indicate an order date.

DTM02 373 Date

Description: Date expressed as

CCYYMMDD

X DT 8/8 Must use 1

DTM03 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 (00-99)

DLMS Note: 1. Use with Code 102 (Issue)

to provide the time of issue.

X TM 4/8 Used 1
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F867I5IA43 14 February 13, 2024

2. Express time in UTC using a

four-position (HHMM) format.

3. Authorized DLMS enhancement; see

introductory DLMS note 5e. on IC cover

page.
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

004010F867I5IA43 15 February 13, 2024

REF Reference Identification Pos: 30 Max: 20

Detail - Optional

Loop: PTD Elements: 4

User Option (Usage): Must use

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:

Must use this 2/REF/030 to identify the materiel and other data pertinent to the transaction.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

REF01 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

DLMS Note: 1. Must use National Stock

Number (NSN), when known, to identify the

materiel, except when appropriate brand

name subsistence items are identified by

the Subsistence Identification Number or

when maintenance/industrial activity

materiel is identified by Local Stock

Number. An exception is also authorized

for CAV where materiel may be identified

by the National Item Identification Number

(NIIN) when the Federal Supply Code

(FSC) is not available.

DLMS Note: 1. Must use National Stock

Number (NSN), when known, to identify the

materiel, except when appropriate brand

name subsistence items are identified by

the Subsistence Identification Number or

when maintenance/industrial activity

materiel is identified by Local Stock

Number. An exception is also authorized

for CAV where materiel may be identified

by the National Item Identification Number

(NIIN) when the Federal Supply Code

(FSC) is not available.

2. For DLMS use, only the following codes

are authorized.

M ID 2/3 Must use 1

Code Name

16 Military Interdepartmental Purchase Request (MIPR) Number

DLMS Note:

1. Use to identify the MIPR number when tracking in-process maintenance; otherwise do not use.

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

1I Department of Defense Identification Code (DoDIC)

DLMS Note:

1. Use to identify ammunition items.

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

6L Agent Contract Number

DLMS Note:

1. Use in GFP-related transactions to identify the procurement instrument identifier (PIID) applicable to

the contract authorizing the contractor to have custody of GFP. Use the legacy procurement instrument

identification number (PIIN) pending transition to the PIID.

2. If GFP is authorized under a PIID call/order number (F in 9th position), provide the PIID call/order

number in the PIID field.

3. Required for Air Force GFP accountability to identify the CICP’s contract number.

4. Authorized DLMS enhancement; see introductory DLMS note 5e on IC cover page. Refer to ADC 

1. Use in GFP-related transactions to identify the procurement instrument identifier (PIID) applicable to

the contract authorizing the contractor to have custody of GFP. Use the legacy procurement instrument

identification number (PIIN) pending transition to the PIID.

2. If GFP is authorized under a PIID call/order number (F in 9th position), provide the PIID call/order

number in the PIID field.

3. Required for Air Force GFP accountability to identify the CICP’s contract number.

4. Authorized DLMS enhancement; see introductory DLMS note 5e on IC cover page. Refer to ADC 
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

Code Name

004010F867I5IA43 16 February 13, 2024

1224.

77 Work Package

DLMS Note:

1. Use to identify a maintenance work order number.

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

86 Operation Number

DLMS Note:

1. Use to identify the Key Operation (KO) Number associated with the JO. 

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

9R Job Order Number

DLMS Note:

1. Use to identify 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 Job Order Number may be repeated as a

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

AH Agreement Number

DLMS Note:

1. Use to identify the Depot Maintenance Inter-Service Support Agreement. Use when tracking

in-process maintenance, otherwise do not use.

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

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:

1. Use in GFP-related transactions to provide contract information associated with the authorizing

shipment of GFP to the contractor.

2. Use to identify the procurement instrument identifier (PIID). Use the legacy procurement instrument

identification number (PIIN) pending transition to the PIID. When GFP 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 a 3 for Research OTs or 9 for Prototype

and Production OTs. Refer to ADC 1161A or ADC 1420.

3. Authorized DLMS enhancement. Refer to ADC 1014 and ADC 1224.

1. Use in GFP-related transactions to provide contract information associated with the authorizing

shipment of GFP to the contractor.

2. Use to identify the procurement instrument identifier (PIID). Use the legacy procurement instrument

identification number (PIIN) pending transition to the PIID. When GFP 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 a 3 for Research OTs or 9 for Prototype

and Production OTs. Refer to ADC 1161A or ADC 1420.

3. Authorized DLMS enhancement. Refer to ADC 1014 and ADC 1224.

CU Clear Text Clause

DLMS Note:

1. Use with 2/PTD01/010 code BQ to provide a clear text description that is not otherwise described by

authorized codes.

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

DO Delivery Order Number

DLMS Note:

1. Use in conjunction with the PIIN (Code 6L) for GFP-related transactions to identify the legacy four

position call/order number associated with the PIIN applicable to the contract authorizing the contractor

to have custody of GFP.

2. Do not use for the PIID call/order number. The PIID call/order number is mapped to Code 6L.

3. Authorized DLMS enhancement; see introductory DLMS note 5e. on IC cover page. Refer to ADC

1224.

1. Use in conjunction with the PIIN (Code 6L) for GFP-related transactions to identify the legacy four

position call/order number associated with the PIIN applicable to the contract authorizing the contractor

to have custody of GFP.

2. Do not use for the PIID call/order number. The PIID call/order number is mapped to Code 6L.

3. Authorized DLMS enhancement; see introductory DLMS note 5e. on IC cover page. Refer to ADC

1224.
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

Code Name

004010F867I5IA43 17 February 13, 2024

FQ Form Number

DLMS Note:

1. Use to identify the form stock number.

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

3. Use REF03 to provide form stock number. Refer to ADC 1287.

MF Manufacturers Part Number

DLMS Note:

1. Use to identify nonstandard materiel.

2. Use REF03 to provide manufacturer’s part number. Refer to ADC 1287.

NS National Stock Number

Q9 Repair Order Number

DLMS Note:

Identifies the Associated Commercial Asset Visibility (CAV) Repair Document Number. Use to cite the

appropriate repair document number (i.e., CAV Repair Cycle Document Number or CAV-Organic

Repair Module (CAV-ORM) Repair Component Document Number), depending upon applicability. CAV

uses with Issue transactions. Refer to ADC 341 and ADC 461.

RV Receiving Number

DLMS Note:

Used in CAV to identify a Previous Movement Document Number. Refer to ADC 341.

S6 Stock Number

DLMS Note:

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

2. When used for a unit of use LSN applicable to NSN materiel, the applicable NSN will be included for

cross-reference. 

3. When used for a unit of use LSN applicable to part numbered items, the original part-numbered item

LSN will also be included for cross-reference.

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

381/Approved Addendum 381A.

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

2. When used for a unit of use LSN applicable to NSN materiel, the applicable NSN will be included for

cross-reference. 

3. When used for a unit of use LSN applicable to part numbered items, the original part-numbered item

LSN will also be included for cross-reference.

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

381/Approved Addendum 381A.

TF Transfer Number

DLMS Note:

CAV uses to identify the Advanced Traceability and Control (ATAC) Indicator. CAV cites ATAC

Indicator ‘1’ for ATAC Reporter which indicates that this shipment is to the ATAC hub for

trans-shipment. DLMS migration enhancement authorized for CAV use only. See introductory DLMS

note 5e. Refer to ADC 341.

TN Transaction Reference Number

DLMS Note:

Must use to identify the document number from the source document.

WF 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 which can reference multiple prime vendor part

numbers for a specific site. Always cite the Local Catalog Identification value in REF03.

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

WL Federal Supply Classification Code

DLMS Note:

1. Use to identify the Federal Supply Classification of nonstandard materiel when a part number is not

available and materiel can only be identified by description (e.g., non-NSN lumber products).

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

WO Work Order Number

DLMS Note:
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

Code Name

004010F867I5IA43 18 February 13, 2024

Use to identify the Build Directive Number for medical/surgical component assembly. A data

maintenance action was approved in version 5010. The approved code/name is “BDN – Build Directive

Number.

WP Warehouse Pick Ticket Number

DLMS Note:

1. Use to identify 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 REF03 due to field length.

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

X9 Internal Control Number

DLMS Note:

Used in CAV to identify a contractor’s reference number. Contractor’s Reference Number is used to

indicate the unique number used by the CAV II System to identify and track EDI transactions. Refer to

ADC 341.

XD Subsistence Identification Number

DLMS Note:

Use to identify subsistence items.

ZZ Mutually Defined

DLMS Note:

Use to identify nonstandard materiel when all other authorized codes do not apply or cannot be

determined (includes management control numbers and locally assigned control numbers). May be

used for DLSS-to-DLMS conversion when the translator cannot determine a more appropriate code.

ABV Book Number

DLMS Note:

Use for publication stock number. This is a DLMS enhancement for future use.

NIN National Item Identification Number

DLMS Note:

1. Use only for CAV when the NSN (FSC plus NIIN) is not available. Refer to ADC 341.

2. Qualifier NIN is a migration code approved for use in X12 version 5020. This is an authorized DLMS

enhancement for use by CAV and by CAV trading partners by mutual agreement.

PWC Preliminary Work Candidate Number

DLMS Note:

1. Use to identify a Requisition Alert Document Number. 

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

SLI Secondary Location Identifier

DLMS Note:

1. Use in combination with purpose code Z to request further segregation below line item. SLI cannot

exceed 6 alpha/numeric characters. 

2. A local code ‘SLI’ is established for use in the 867I, version 4010. A data maintenance action has

been submitted for establishment of ‘SLI- Secondary Location Identifier’ in a future version.

REF02 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 1

REF03 352 Description

Description: A free-form description to

clarify the related data elements and their

content

DLMS Note: 1. Use only with REF01 codes

CU, FQ, MF, WF and WP. 

X AN 1/80 Used 1
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F867I5IA43 19 February 13, 2024

2. Use with REF01 code CU to identify

issue category information.

3. DMLSS/TEWLS use with REF01 code

WF to identify the Local Catalog

Identification.

4. Use with REF01 code WP to cite the

picklist control number. 

REF04 C040 Reference Identifier

Description: To identify one or more

reference numbers or identification

numbers as specified by the Reference

Qualifier

Syntax: 

1. P0304 - If either C04003 or C04004 is

present, then the other is required.

2. P0506 - If either C04005 or C04006 is

present, then the other is required.

O Comp Used 1

REF04-01 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

DLMS Note: For DLMS use, only the

following codes are authorized.

M ID 2/3 Must use 1

Code Name

1Y Repair Action Number

DLMS Note:

1. Use with REF01 code AH to identify the DMISA line number. Use when tracking in-process

maintenance, otherwise do not use.

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

NS National Stock Number

DLMS Note:

1. Use to identify the NSN.

2. The NSN is provided as a cross-reference when unit of use indicator is included and the Local Stock

Number (LSN) is identified as the primary materiel identification. Authorized DLMS enhancement under

DLA industrial activity support agreement.

OQ Order Number

DLMS Note:

1. Use as directed by the authorizing Service/Agency in GFP-related transactions with REF01 Code CT

to identify the legacy four-position call/order number associated with the PIIN.

2. Do not use for the PIID call/order number. The PIID call/order number is mapped to REF01 Code

CT. Refer to ADC 1161A.

3. Authorized DLMS enhancement. Refer to ADC 1014.

PG Product Group

DLMS Note:

Must use with REF01 code WL to identify the materiel name or description.

S6 Stock Number

DLMS Note:

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

2. The LSN is provided as a cross-reference when unit of use indicator is included and the unit of use

LSN is identified as the primary materiel identification. Authorized DLMS enhancement under DLA

industrial activity support agreement.

W7 Commercial and Government Entity (CAGE) Code
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

Code Name

004010F867I5IA43 20 February 13, 2024

DLMS Note:

Use with REF01 code MF to uniquely identify the manufacturer's part number.

W8 Suffix

DLMS Note:

1. Use with REF01 code TN to identify the issue document number suffix.

2. Use with REF01 code RV to identify the Previous Movement Document Number Suffix.

3. When used in association with the Requisition Alert Document Number (Qualifier PWC, above), this

will be the requisition alert document suffix. The Requisition Alert Document Number Suffix is an

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

REF04-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 1

REF04-03 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

O ID 2/3 Used 1

Code Name

C7 Contract Line Item Number

DLMS Note:

1. Use as directed by the authorizing Service/Agency in GFP-related transactions to associate a

Contract Line Item Number with the Contract Number.

2. Authorized DLMS enhancement; Refer to ADC 1014

REF04-04 127 Reference Identification

Description: Reference information as

defined for a particular Transaction Set or

as specified by the Reference Identification

Qualifier

O AN 1/30 Used 1

REF04-05 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

O ID 2/3 Used 1

Code Name

W8 Suffix

DLMS Note:

Use to identify DTID Number Suffix when applicable.

REF04-06 127 Reference Identification

Description: Reference information as

defined for a particular Transaction Set or

as specified by the Reference Identification

Qualifier

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

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

004010F867I5IA43 21 February 13, 2024

N1 Name Pos: 50 Max: 1

Detail - Optional

Loop: N1 Elements: 4

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 at least one iteration of this 2/N1/050 loop to identify the organization to receive the transaction (N106 code TO with appropriate

N101 code). 

2. Use additional iterations to identify other organizations associated with the transaction.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N101 98 Entity Identifier Code

Description: Code identifying an

organizational entity, a physical location,

property or an individual

DLMS Note: For DLMS use, only the

following codes are authorized.

M ID 2/3 Must use 1

Code Name

CN Consignee

DLMS Note:

1. Use in CAV transactions to indicate a Ship to DoDAAC.

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

3. Authorized DLMS enhancement for Inter-Service Ammunition use to identify consignee (DIC

BG1/BG2 rp 66-71). Use with N103 code 10-DODAAC. DLMS Component unique enhancement. See

introductory DLMS note 5f. Refer to ADC 261 and ADC 445.

KK Registering Party

DLMS Note:

1. Use to identify the Component UIT registry. May be used by a Component when their UIT process

requires that a copy of the transaction also be sent to a UIT registry for information purposes. Must be

used with 2/N106/50 code ‘PK-Party to Receive Copy’ to identify that this is only an information copy of

the transaction, for use with the Component UIT registry. Cite the applicable Routing Identifier in

2/N103. 

2. Authorized DLMS enhancement for Air Force and DSS use with PIC NWRM UIT; For PIC UIT, must

use in conjunction with 2/N106 code PK and 1/BPT07/20 Action Code FI and cite the applicable

Routing Identifier in 2/N103. 

3. Except as noted above, DLMS enhancement; see introductory DLMS note 5a.

1. Use to identify the Component UIT registry. May be used by a Component when their UIT process

requires that a copy of the transaction also be sent to a UIT registry for information purposes. Must be

used with 2/N106/50 code ‘PK-Party to Receive Copy’ to identify that this is only an information copy of

the transaction, for use with the Component UIT registry. Cite the applicable Routing Identifier in

2/N103. 

2. Authorized DLMS enhancement for Air Force and DSS use with PIC NWRM UIT; For PIC UIT, must

use in conjunction with 2/N106 code PK and 1/BPT07/20 Action Code FI and cite the applicable

Routing Identifier in 2/N103. 

3. Except as noted above, DLMS enhancement; see introductory DLMS note 5a.

LG Location of Goods

DLMS Note:

1. Use to identify the physical location of GFP while in CICP custody. The location may be the CICP,

the CICP’s warehouse or subcontractor. This location must be identified by DoDAAC. 
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

Code Name

004010F867I5IA43 22 February 13, 2024

2. Must use for Air Force GFP accountability. Refer to ADC 1224.

OW Owner of Property or Unit

DLMS Note:

For Air Force GFP accountability, use to identify the Air Force program manager in the accountable

property system of record (APSR). Must identify the program manager by RIC. If the program

manager DoDAAC does not have an assigned RIC, use the generic Air Force GFP APSR RIC with

2/N106=TO and use a second iteration of the N1 loop (repeating Code OW without 2/N106=TO) to

provide the program manager DoDAAC. Refer to ADC 1224.

PW Pick Up Address

DLMS Note:

1. Use in CAV transactions to indicate a materiel pick-up address.

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

UQ Subsequent Owner

DLMS Note:

Use for inter-Service ammunition or ammunition-related ownership transfer with no physical movement

of materiel. Use to identify 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.

Z4 Owning Inventory Control Point

DLMS Note:

Use to identify the inventory control organization to which the transaction is being sent.

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 1

Code Name

10 Department of Defense Activity Address Code (DODAAC)

DLMS Note:

1. DLMS enhancement; see introductory DLMS note 5a.

2. Authorized DLMS enhancement for Inter-Service Ammunition use with N101 code CN to identify

consignee DODAAC (DIC BG1/BG2 rp 66-71). See introductory DLMS note 5f. (Refer to ADC 261 and

ADC 445.)

3. Authorized for use by Air Force CICP to identify other organizations associated with the transaction

by DODAAC. (Refer to ADC 1224A).

1. DLMS enhancement; see introductory DLMS note 5a.

2. Authorized DLMS enhancement for Inter-Service Ammunition use with N101 code CN to identify

consignee DODAAC (DIC BG1/BG2 rp 66-71). See introductory DLMS note 5f. (Refer to ADC 261 and

ADC 445.)

3. Authorized for use by Air Force CICP to identify other organizations associated with the transaction

by DODAAC. (Refer to ADC 1224A).

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.

M4 Department of Defense Routing Identifier Code (RIC)

UR Uniform Resource Locator (URL)

DLMS Note:

1. Use when appropriate to identify the Component UIT registry.

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

N104 67 Identification Code

Description: Code identifying a party or

X AN 2/80 Must use 1
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F867I5IA43 23 February 13, 2024

other code

N106 98 Entity Identifier Code

Description: Code identifying an

organizational entity, a physical location,

property or an individual

O ID 2/3 Used 1

Code Name

PK Party to Receive Copy

DLMS Note:

1. Use when appropriate to send an information copy of the transaction to a Component UIT registry.

For use with N101 code KK. 

2. Authorized DLMS enhancement for Air Force and DSS use with PIC NWRM UIT. For PIC UIT, must

use in conjunction with 2/N101 code KK and 1/BPT07/20 Action Code FI and cite the applicable

Routing Identifier in 2/N103. 

3. Except as noted above, DLMS enhancement; see introductory DLMS note 5a.

1. Use when appropriate to send an information copy of the transaction to a Component UIT registry.

For use with N101 code KK. 

2. Authorized DLMS enhancement for Air Force and DSS use with PIC NWRM UIT. For PIC UIT, must

use in conjunction with 2/N101 code KK and 1/BPT07/20 Action Code FI and cite the applicable

Routing Identifier in 2/N103. 

3. Except as noted above, DLMS enhancement; see introductory DLMS note 5a.

TO Message To

DLMS Note:

Use to indicate the organization cited in N104 is receiving the transaction.
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

004010F867I5IA43 24 February 13, 2024

QTY Quantity Pos: 110 Max: 1

Detail - Optional

Loop: QTY Elements: 3

User Option (Usage): Must use

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.

DLMS Note:

1. Use the 2/QTY/110 loop to identify quantity information and provide additional descriptive information about the issue transaction. 

2. Use a single 2/QTY/110 loop for each issue transaction (except issues to DRMO, PTD01 code BI) to identify the quantity issued. For

issues to DRMO use a second 2/QTY/110 loop iteration, as needed, to identify the quantity retained in stock.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

QTY01 673 Quantity Qualifier

Description: Code specifying the type of

quantity

DLMS Note: For DLMS use, only the

following codes are authorized.

M ID 2/2 Must use 1

Code Name

V1 Retention Quantity

DLMS Note:

1. Use to identify the quantity retained in stock after an issue to DRMO.

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

V3 Transfer Quantity

DLMS Note:

Must use to identify the quantity issued. To reverse all or part of an issue transaction, use a minus sign

in front of the quantity to be reversed.

QTY02 380 Quantity

Description: Numeric value of quantity

DLMS Note: 1. Express as a whole

number with no decimals. 

2. A field size exceeding 5 positions (seven

for FSG 13, ammunition) may not be

received or understood by recipient's

automated processing system. See

introductory DLMS note 5d.

X R 1/15 Must use 1

QTY03 C001 Composite Unit of Measure

Description: To identify a composite unit of

measure(See Figures Appendix for

examples of use)

O Comp Must use 1

QTY03-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

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

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F867I5IA43 25 February 13, 2024

taken

DLMS Note: 1. Use to identify the unit of

issue for issued materiel. 

2. DLMS users see the Unit of Issue and

Purchase Unit Conversion Table for

available codes.
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

004010F867I5IA43 26 February 13, 2024

AMT Monetary Amount Pos: 140 Max: 12

Detail - Optional

Loop: QTY Elements: 2

User Option (Usage): Used

Purpose: To indicate the total monetary amount

DLMS Note:

1. Use only for Army Medical Material Agreement (AMMA) issues of materiel.

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

AMT01 522 Amount Qualifier Code

Description: Code to qualify amount

DLMS Note: For DLMS use only the

following codes are authorized.

M ID 1/3 Must use 1

Code Name

JJ Cost Basis

DLMS Note:

1. Use only for AMMA issues of materiel to identify the latest acquisition cost of the materiel.

2. DLMS enhancement. See introductory DLMS note 5a. Under DLMS the latest acquisition cost will be

expressed as R9.2.

NT Unit Value

DLMS Note:

Use to identify the unit price applicable to the materiel identified by the issued. Authorized DLMS

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

AMT02 782 Monetary Amount

Description: Monetary amount

M R 1/18 Must use 1
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

004010F867I5IA43 27 February 13, 2024

MEA Measurements Pos: 160 Max: 40

Detail - Optional

Loop: QTY 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:

1. DLMS enhancement. See introductory DLMS note 5a.

2. Authorized DLMS migration enhancement for CAV use only. See introductory DLMS note 5e. Refer to ADC 341. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

MEA01 737 Measurement Reference ID Code

Description: Code identifying the broad

category to which a measurement applies

DLMS Note: For DLMS use, only the

following codes are authorized.

O ID 2/2 Used 1

Code Name

SD Shipped Dimensions

DLMS Note:

CAV uses to identify the Cube Value which represents the dimension of the item issued. Expressed as

10 numeric, 6v4 (6 positions to the left of the decimal and 4 positions to the right. Do not enter leading

zeros, nor a decimal point.

WT Weights

DLMS Note:

CAV uses to identify the gross size or weight of the tem issued. Expressed as 9 numeric, 7v2 (7

positions to the left of the decimal and 2 positions to the right. Do not enter leading zeros, nor a

decimal point.

MEA02 738 Measurement Qualifier

Description: Code identifying a specific

product or process characteristic to which a

measurement applies

DLMS Note: For DLMS use, only the

following codes are authorized.

O ID 1/3 Used 1

Code Name

U Weight per Unit

DLMS Note:
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

Code Name

004010F867I5IA43 28 February 13, 2024

Use with MEA01 code WT.

UCB Cube

DLMS Note:

Use with MEA01 code SD.

MEA03 739 Measurement Value

Description: The value of the

measurement

O R 1/20 Used 1
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

004010F867I5IA43 29 February 13, 2024

DD Demand Detail Pos: 240 Max: 1

Detail - Optional

Loop: QTY 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:

Use to identify the demand code, weapon system, and requisitioner stocking information.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

DD01 1271 Industry Code

Description: Code indicating a code from a

specific industry code list

X AN 1/30 Must use 1

DD02 1270 Code List Qualifier Code

Description: Code identifying a specific

industry code list

O ID 1/3 Must use 1

Code Name

74 Demand Code

DLMS Note:

DLMS enhancement; see introductory DLMS note 5a.

DD03 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

X ID 2/3 Used 1

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 5a.

DD04 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 1

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

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

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F867I5IA43 30 February 13, 2024

which this demand is reported.

DD06 1270 Code List Qualifier Code

Description: Code identifying a specific

industry code list

O ID 1/3 Used 1

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 5a.

DD07 380 Quantity

Description: Numeric value of quantity

DLMS Note: 1. Use to identify the quantity

associated with the weapon system and

associated demand code. 

2. A field size exceeding 5 positions (seven

for FSG 13, ammunition) may not be

received or understood by recipient's

automated processing system. See

guideline note 4d.

3. DLMS enhancement; see introductory

DLMS note 4a.

O R 1/15 Used 1

DD09 1271 Industry Code

Description: Code indicating a code from a

specific industry code list

X AN 1/30 Used 1

DD10 1270 Code List Qualifier Code

Description: Code identifying a specific

industry code list

O ID 1/3 Used 1

Code Name

98 Reason for Requisitioning Code

DLMS Note:

DLMS enhancement; see guideline note 5a.
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

004010F867I5IA43 31 February 13, 2024

LM Code Source Information Pos: 260 Max: 1

Detail - Optional

Loop: LM Elements: 1

User Option (Usage): Must use

Purpose: To transmit standard code list identification information

Comments: 

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

DLMS Note:

Use this 2/LM/260 loop to identify coded information maintained in departmental or agency documentation.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LM01 559 Agency Qualifier Code

Description: Code identifying the agency

assigning the code values

M ID 2/2 Must use 1

Code Name

DF Department of Defense (DoD)
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

004010F867I5IA43 32 February 13, 2024

LQ Industry Code Pos: 270 Max: 100

Detail - Optional

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 Rep

LQ01 1270 Code List Qualifier Code

Description: Code identifying a specific

industry code list

DLMS Note: 1. Use either code 99 or A1

(but not both), except for ammunition where

both codes may be used. (Use of both

codes for ammunition is a DLMS

enhancement (see introductory DLMS note

5a.)

DLMS Note: 1. Use either code 99 or A1

(but not both), except for ammunition where

both codes may be used. (Use of both

codes for ammunition is a DLMS

enhancement (see introductory DLMS note

5a.)

2. For DLMS use, only the following codes

are authorized

O ID 1/3 Must use 1

Code Name

0 Document Identification Code

DLMS Note:

1. The DLSS DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLSS/DLMS

environment. Continued support of the DIC in a full DLMS environment will be assessed at a future

date.

2. In a mixed DLSS-DLMS environment, for Inter-Service Ammunition interface, when including

BG1/BG2 data, must use 2 iterations of LQ to provide DIC D7_ as well as either DIC BG1 or BG2 as

applicable, to alert DAAS of BG1/ BG2 requirement for non-DLMS Ammunition system trading partners:

Naval Operational Logistics Support Center (NOLSC) Ordnance Information System-Wholesale

(OIS-W), Program Manager for Ammunition, Marine Corps Systems Command (MARCORSYSCOM)

Ordnance Information System-Marine Corps (OIS-M),and Warner Robins Air Logistics Center Combat

Ammunition System (CAS).

3. Future streamlined data; see introductory DLMS note 5c.

1. The DLSS DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLSS/DLMS

environment. Continued support of the DIC in a full DLMS environment will be assessed at a future

date.

2. In a mixed DLSS-DLMS environment, for Inter-Service Ammunition interface, when including

BG1/BG2 data, must use 2 iterations of LQ to provide DIC D7_ as well as either DIC BG1 or BG2 as

applicable, to alert DAAS of BG1/ BG2 requirement for non-DLMS Ammunition system trading partners:

Naval Operational Logistics Support Center (NOLSC) Ordnance Information System-Wholesale

(OIS-W), Program Manager for Ammunition, Marine Corps Systems Command (MARCORSYSCOM)

Ordnance Information System-Marine Corps (OIS-M),and Warner Robins Air Logistics Center Combat

Ammunition System (CAS).

3. Future streamlined data; see introductory DLMS note 5c.

Z Cancellation Reason

DLMS Note:

1. Use for the Reason for Reversal Code.

2. Navy uses the Reason for Reversal Code for Navy issue reversal codes B and S in support of legacy

requirements. Refer to ADC 259.

3. By DLMS enhancement, DLA storage activities must cite the Reason for Reversal Code on all issue

reversals associated with a validated SDR. Refer to ADC 1160. 

4. A data maintenance action was approved in version 5050. The approved code/name is “RRC –

Reason for Reversal Code”.

1. Use for the Reason for Reversal Code.

2. Navy uses the Reason for Reversal Code for Navy issue reversal codes B and S in support of legacy

requirements. Refer to ADC 259.

3. By DLMS enhancement, DLA storage activities must cite the Reason for Reversal Code on all issue

reversals associated with a validated SDR. Refer to ADC 1160. 

4. A data maintenance action was approved in version 5050. The approved code/name is “RRC –

Reason for Reversal Code”.

78 Project Code

DLMS Note:

1. Use for all issue transactions to identify special programs, exercises, projects, operations, and other

purposes; except issues to DLA Disposition Services.
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

Code Name

004010F867I5IA43 33 February 13, 2024

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 for all issue transactions except issues to DRMO to identify the supply priority of the transaction.

80 Advice Code

DLMS Note:

Use for all issue transactions except issues to DRMO to convey information which was significant to

processing the requirement.

83 Supply Condition Code

DLMS Note:

Must use to identify the supply condition of the materiel issued.

84 Management Code

87 Subsistence Type of Pack Code

DLMS Note:

Use only for subsistence items to identify type of pack information.

88 Disposal Authority Code

DLMS Note:

1. Use only for disposal issue transactions to identify that items being transferred to disposal are

authorized for transfer by the proper authority.

2. Authorized DLMS enhancement; see introductory DLMS note 5e. on IC cover page.

90 Precious Metals Indicator Code

DLMS Note:

1. Use only for disposal issue transactions to identify the precious metals content of materiel being

transferred to disposal.

2. Authorized DLMS enhancement; see introductory DLMS note 5e. on IC cover page.

91 Automated Data Processing Equipment Identification Code

DLMS Note:

1. Use only for disposal issue transactions to identify ADP equipment that is being transferred to

disposal.

2. Authorized DLMS enhancement; see introductory DLMS note 5e. on IC cover page.

92 Reason for Disposal Code

DLMS Note:

1. Use only for disposal issue transactions to identify the reason that an item is being transferred to

disposal.

2. Authorized DLMS enhancement; see introductory DLMS note 5e. on IC cover page.

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 5a.

98 Reason for Requisitioning Code

DLMS Note:

1. Use to identify the requisitioner's need for the requested materiel.

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

99 Purpose Code

A1 Ownership Code

DLMS Note:

When used for inter-Service ammunition-related ownership transfer with no physical movement of

materiel, use to identify the new/gaining (to) ownership code. Refer to ADC 1020.
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

Code Name

004010F867I5IA43 34 February 13, 2024

A7 Record Control Number

DLMS Note:

Commercial Asset Visibility (CAV) uses to identify the Advanced Traceability and Control (ATAC)

Indicator. CAV cites ATAC Indicator ‘1’ for ATAC Reporter which indicates that this shipment is to the

ATAC hub for trans-shipment. Authorized for CAV use. See PDC 351.

A9 Supplemental Data

DLMS Note:

1. Use to identify supplementary address/supplemental data.

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

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 5c.

5. During DLSS/DLMS transition, use on issue transactions for inter-Service ammunition or

ammunition-related ownership transfer with no physical movement of materiel and no billing. Cite

Signal Code M 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 supplementary address/supplemental data.

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

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 5c.

5. During DLSS/DLMS transition, use on issue transactions for inter-Service ammunition or

ammunition-related ownership transfer with no physical movement of materiel and no billing. Cite

Signal Code M 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.

AK Distribution Code

DLMS Note:

Future streamlined data; see introductory DLMS note 5c.

DE Signal Code

DLMS Note:

Future streamlined data; see introductory DLMS note 5c.

DF Media and Status Code

DLMS Note:

Future streamlined data; see introductory DLMS note 5c.

FC Type Physical Inventory or Transaction History Code

DLMS Note:

1. Use only with 1/BPT07/20 Action Code W1.

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

FD Demilitarization Code

DLMS Note:

1. Use only for DRMO issue transactions to identify demilitarization information for materiel being

transferred to disposal.

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

GQ Group Qualifier Code

DLMS Note:

Use to identify the 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 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.

RD Property Ownership Type Code

DLMS Note:

Use only for inter-Service ammunition-related ownership transfer with no physical movement of

materiel. Use to identify the old (from) ownership code. DLMS enhancement. Refer to ADC 1020.
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

Code Name

004010F867I5IA43 35 February 13, 2024

RT Request Type

DLMS Note:

Use for the Navy Issue on Request Code. DLMS enhancement authorized for use by Navy and DLA

Distribution Standard System. 

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.

IMC Item Management Code

DLMS Note:

1. Use to identify the Item Management Code (IMC) for integrated material management. 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.

MCC Material Control Code

DLMS Note:

1. Use to identify the Material Control Code (MCC) for special inventory reporting. 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.

SMI Special Material Identification Code

DLMS Note:

1. Use to identify the Special Material Identification Code (SMIC) for an 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.

SRC List of codes identifying DoD Serialized Report Type Code

DLMS Note:

1. Use to cite the Air Force Serialized Report Code. The Air Force uses this code to indicate that an

item requires serialized management. Applicable to property identified by national stock number (NSN)

or Air Force-assigned local stock number (LSN) in accordance with CICP contract requirements. 

Authorized for Air Force GFP-A. Refer to ADC 1230A.

2. Migration code SRC is established for use in the 867I version 4010. A data maintenance action was

approved in version 8010. The approved code/name is "SRC - List of codes identifying DoD Serialized

Report Type Code.

The following values will be conveyed in 2/LQ02/130:

A Small Arms

C Communications Security (COMSEC)

D Reserved

R Nuclear Weapons Related Material (NWRM) COMSEC

W NWRM

1. Use to cite the Air Force Serialized Report Code. The Air Force uses this code to indicate that an

item requires serialized management. Applicable to property identified by national stock number (NSN)

or Air Force-assigned local stock number (LSN) in accordance with CICP contract requirements. 

Authorized for Air Force GFP-A. Refer to ADC 1230A.

2. Migration code SRC is established for use in the 867I version 4010. A data maintenance action was

approved in version 8010. The approved code/name is "SRC - List of codes identifying DoD Serialized

Report Type Code.

The following values will be conveyed in 2/LQ02/130:

A Small Arms

C Communications Security (COMSEC)

D Reserved

R Nuclear Weapons Related Material (NWRM) COMSEC

W NWRM

T05 Inspection Parameters

DLMS Note:

1. Use to identify the Quality Inspection Code indicating the quality level of inspection which the item

must be procured and inspected to. 

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 1
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F867I5IA43 36 February 13, 2024
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

004010F867I5IA43 37 February 13, 2024

LX Assigned Number Pos: 280 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 the LX segment as a counter to identify the number of 2/LX/280 loop iterations in the transaction set.

2. The entire 2/LX//280 loop (LOOP ID - LX) is an authorized DLMS enhancement for use to provide item unique identification (IUID) data as

noted below for specific implementations; see introductory DLMS note 5e. For all other applications, see introductory DLMS note 5a.

3. The 2/LX/280 loop is repeated for each item to be uniquely identified and provides flexibility to accommodate tracking by serial

number/UII.

4. May use the 2/LX/280 loop to provide batch/lot number information.

5. Authorized for use with the Positive Inventory Control (PIC) Nuclear Weapon Related Materiel (NWRM) UIT program (UIT Designator

AAJ). Refer to ADC 347 and ADC 1136.

6. Authorized for use for Air Force GFP accountability of serially tracked assets between the Air Force CICP and the Air Force APSR

systems. Refer to ADC 1230A.

1. Use the LX segment as a counter to identify the number of 2/LX/280 loop iterations in the transaction set.

2. The entire 2/LX//280 loop (LOOP ID - LX) is an authorized DLMS enhancement for use to provide item unique identification (IUID) data as

noted below for specific implementations; see introductory DLMS note 5e. For all other applications, see introductory DLMS note 5a.

3. The 2/LX/280 loop is repeated for each item to be uniquely identified and provides flexibility to accommodate tracking by serial

number/UII.

4. May use the 2/LX/280 loop to provide batch/lot number information.

5. Authorized for use with the Positive Inventory Control (PIC) Nuclear Weapon Related Materiel (NWRM) UIT program (UIT Designator

AAJ). Refer to ADC 347 and ADC 1136.

6. Authorized for use for Air Force GFP accountability of serially tracked assets between the Air Force CICP and the Air Force APSR

systems. Refer to ADC 1230A.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LX01 554 Assigned Number

Description: Number assigned for

differentiation within a transaction set

DLMS Note: In the first 2/LX/280 loop

iteration, cite numeric 1. In each

subsequent loop iteration, increase

incrementally by 1.

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

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

004010F867I5IA43 38 February 13, 2024

REF Reference Identification Pos: 290 Max: >1

Detail - Optional

Loop: LX Elements: 4

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. The 2/REF/290 loop is an authorized DLMS enhancement for intra-Component use in Issue transactions to provide Item Unique

Identification (IUID) serial number/UII data as noted below for specific implementations; see introductory DLMS note 5e. For all other

applications, see introductory DLMS note 5a. 

2. This transaction will support item identification based upon serial number/UII. This transaction also provides for use of a batch/lot

number, when applicable.

3. Use multiple iterations of 2/REF/290 segment within the 2/LX/280 loop, to provide identifying information for an item as needed.

4. Authorized for use with the Positive Inventory Control (PIC) Nuclear Weapon Related Materiel (NWRM) UIT program (UIT Designator

AAJ). Refer to ADC 347 and ADC 1136.

5. Authorized for use with Air Force GFP accountability. Refer to ADC 1230A.

1. The 2/REF/290 loop is an authorized DLMS enhancement for intra-Component use in Issue transactions to provide Item Unique

Identification (IUID) serial number/UII data as noted below for specific implementations; see introductory DLMS note 5e. For all other

applications, see introductory DLMS note 5a. 

2. This transaction will support item identification based upon serial number/UII. This transaction also provides for use of a batch/lot

number, when applicable.

3. Use multiple iterations of 2/REF/290 segment within the 2/LX/280 loop, to provide identifying information for an item as needed.

4. Authorized for use with the Positive Inventory Control (PIC) Nuclear Weapon Related Materiel (NWRM) UIT program (UIT Designator

AAJ). Refer to ADC 347 and ADC 1136.

5. Authorized for use with Air Force GFP accountability. Refer to ADC 1230A.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

REF01 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

DLMS Note: For DLMS use, only the

following codes are authorized.

M ID 2/3 Must use 1

Code Name

BT Batch Number

DLMS Note:

Use to identify the batch, lot, or other number identifying the production run. The batch/lot number may

not exceed 20 characters in accordance with IUID policy.

SE Serial Number

DLMS Note:

Use to identify the serial number. Place serial number value in REF02. The serial number may not

exceed 30 characters in accordance with IUID policy.

U3 Unique Supplier Identification Number (USIN)

DLMS Note:

1. Use to identify the UII. Place UII value in REF03. The UII may not exceed 50 characters in

accordance with IUID Policy. 

2. 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: Use to indicate serial number

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

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F867I5IA43 39 February 13, 2024

when REF01=SE.

REF03 352 Description

Description: A free-form description to

clarify the related data elements and their

content

DLMS Note: Use to indicate UII value when

REF01=U3.

X AN 1/80 Used 1

REF04 C040 Reference Identifier

Description: To identify one or more

reference numbers or identification

numbers as specified by the Reference

Qualifier

Syntax: 

1. P0304 - If either C04003 or C04004 is

present, then the other is required.

2. P0506 - If either C04005 or C04006 is

present, then the other is required.

O Comp Used 1

REF04-01 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

DLMS Note: For DLMS use only the

following codes are authorized.

M ID 2/3 Must use 1

Code Name

0N Attached To

DLMS Note:

Authorized DLMS enhancement for Inter-Service Ammunition use. Use when REF01=BT to identify the

Lot Size for the lot number identified in REF02. DLMS Component unique enhancement (DIC BG1/BG2,

rp 25-29). See introductory DLMS note 5f. Refer to ADC 261 and ADC 445.

REF04-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 1
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

004010F867I5IA43 40 February 13, 2024

DTM Date/Time Reference Pos: 300 Max: 1

Detail - Optional

Loop: LX Elements: 4

User Option (Usage): Used

Purpose: To specify pertinent dates and times

Syntax Rules: 

1. R020305 - At least one of DTM02, DTM03 or DTM05 is required.

2. C0403 - If DTM04 is present, then DTM03 is required.

3. P0506 - If either DTM05 or DTM06 is present, then the other is required.

DLMS Note:

Use to identify dates associated with the item. If only a date of manufacture or warranty expiration date is required, express the required

date in DTM01/02. If both dates are required, convey the date of manufacture in DTM01/02, and the warranty expiration date in DTM06.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

DTM01 374 Date/Time Qualifier

Description: Code specifying type of date

or time, or both date and time

DLMS Note: For DLMS use, only the

following codes are authorized.

M ID 3/3 Must use 1

Code Name

036 Expiration

DLMS Note:

Authorized DLMS enhancement for Inter-Service Ammunition use to identify the expiration date of the

reported item. DLMS Component unique enhancement (DIC BG1/BG2, rp 9-11). See introductory note

5f. Refer to ADC 261 and ADC 445.

094 Manufacture

DLMS Note:

1. Use to identify the date of manufacture for the materiel identified 

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

302 Maintenance

DLMS Note:

Use to identify the maintenance due date (the date that maintenance is due on the item). Authorized

DLMS enhancement for Inter-Service Ammunition use. DLMS Component unique enhancement (DIC

BG1/BG2, rp 9-11). See introductory note 5f. Refer to ADC 261 and ADC 445.

512 Warranty Expiration

DLMS Note:

1. Use to identify the warranty expiration date associated with the materiel reported.

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

DTM02 373 Date

Description: Date expressed as

CCYYMMDD

X DT 8/8 Must use 1

DTM05 1250 Date Time Period Format Qualifier

Description: Code indicating the date

format, time format, or date and time format

X ID 2/3 Used 1

Code Name

D8 Date Expressed in Format CCYYMMDD
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F867I5IA43 41 February 13, 2024

DTM06 1251 Date Time Period

Description: Expression of a date, a time,

or range of dates, times or dates and times

DLMS Note: 1. Use to indicate the

warranty expiration date when a date of

manufacture is identified in DTM01/02.

2. Identify the date in a CCYYMMDD

format.

X AN 1/35 Used 1
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

004010F867I5IA43 42 February 13, 2024

N1 Name Pos: 310 Max: 1

Detail - Optional

Loop: LX 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:

Use to identify the manufacturer of the UIT item.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N101 98 Entity Identifier Code

Description: Code identifying an

organizational entity, a physical location,

property or an individual

DLMS Note: For DLMS use, only the

following codes are authorized.

M ID 2/3 Must use 1

Code Name

MF Manufacturer of Goods

DLMS Note:

DLMS enhancement; see introductory DLMS note 5a.

N103 66 Identification Code Qualifier

Description: Code designating the

system/method of code structure used for

Identification Code (67)

DLMS Note: For DLMS use, only the

following codes are authorized.

X ID 1/2 Must use 1

Code Name

33 Commercial and Government Entity (CAGE)

DLMS Note:

DLMS enhancement; see introductory DLMS note 5a.

N104 67 Identification Code

Description: Code identifying a party or

other code

X AN 2/80 Must use 1
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

004010F867I5IA43 43 February 13, 2024

FA1 Type of Financial Accounting Data Pos: 340 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 Rep

FA101 559 Agency Qualifier Code

Description: Code identifying the agency

assigning the code values

DLMS Note: 1. 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: 1. 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.

2. DLMS enhancement; see introductory

DLMS note 5a. Applies to all codes listed.

M ID 2/2 Must use 1

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 1

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

DLMS Note:

Use for both materiel and related services.

F060 Other Accessorial Service Charge

F560 Premium Transportation
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

Code Name

004010F867I5IA43 44 February 13, 2024

I260 Transportation Direct Billing

DLMS Note:

Use for non-premium transportation.

R060 Packing, Crating, and Handling Charge
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

004010F867I5IA43 45 February 13, 2024

FA2 Accounting Data Pos: 350 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/350 segment to identify the various components of the line of accounting.

2. 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. Refer to ADC 1043.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

FA201 1196 Breakdown Structure Detail Code

Description: Codes identifying details

relating to a reporting breakdown structure

tree

DLMS Note: DLMS enhancement; see

introductory DLMS note 5a. Applies to all

codes listed.

M ID 2/2 Must use 1

Code Name

89 Budget Line Item Identification

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “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 5e.

90 Project/Task

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “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 5e.

A1 Department Indicator

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Department Regular”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory note 5e.

A2 Transfer from Department

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Department Transfer”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory note 5e.

A4 Basic Symbol Number

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Main Account”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5e.

A5 Sub-class

DLMS Note:

1. Reserved for DoD SLOA/Accounting Classification use to identify “Sub Class”. Refer to ADC 1043.
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

Code Name

004010F867I5IA43 46 February 13, 2024

2. Sub Class is a potential future DLMS enhancement; see introductory DLMS note 5a.

A6 Sub-Account Symbol

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Sub Account”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5e.

AI Activity Identifier

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Activity Identifier”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5e.

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 “Sub-Allocation (formerly known as

Limit/Subhead)”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5e.

B5 Fund Code

BE Business Event Type Code

DLMS Note:

1. Reserved for DoD SLOA/Accounting Classification use to identify “Business Event Type Code”. 

Refer to ADC 1043.

2. Business Event Type Code is a potential future DLMS enhancement; see introductory DLMS note 5a.

3. Qualifier BE is a migration code approved for use in X12 version 7020.

C3 Budget Restriction

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Availability Type”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5e.

CC Cost Center Identifier

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Cost Center Identifier”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5e.

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 “Object Class”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5e.

FA Functional Area

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Functional Area”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5e.

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 “Funding Center Identifier”. Refer to ADC

1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5e.
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

Code Name

004010F867I5IA43 47 February 13, 2024

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 “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 5e.

H1 Cost Code

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Cost Element Code”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5e.

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 5e.

3. Qualifier IA is a migration code approved for use in X12 version 7020.

L1 Accounting Installation Number

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Agency Accounting Identifier”. Refer to

ADC 1043. 

2. Authorized DLMS enhancement; see introductory DLMS note 5e.

P1 Disbursing Station Number

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Agency Disbursing Identifier Code”. Refer

to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5e.

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 5e.

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 5d. 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 5d. 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 5e. 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 5e. 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.
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

Code Name

004010F867I5IA43 48 February 13, 2024

WO Work Order Number

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Work Order Number”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5e.

3. Qualifier WO is a migration code approved for use in X12 version 7020.

YB Beginning Period of Availability

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Beginning Period of Availability Fiscal Year

Date”. Refer to ADC 1043.

2. Use as appropriate to represent Program Year. Availability Type Code must be “X”. Refer to ADC

1043B.

3. Authorized DLMS enhancement; see introductory DLMS note 5e.

4. Qualifier YB is a migration code approved for use in X12 version 7020.

1. For DoD SLOA/Accounting Classification use to identify “Beginning Period of Availability Fiscal Year

Date”. Refer to ADC 1043.

2. Use as appropriate to represent Program Year. Availability Type Code must be “X”. Refer to ADC

1043B.

3. Authorized DLMS enhancement; see introductory DLMS note 5e.

4. Qualifier YB is a migration code approved for use in X12 version 7020.

YE Ending Period of Availability

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Ending Period of Availability Fiscal Year

Date”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory DLMS note 5e.

3. 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 1
DLMS Implementation Convention (IC)

867I Issue

ADC 77, 153, 165, 197, 201, 235, 259, 261, 271, 295, 341, 347, 373, 381, 381A, 409, 435, 436, 445, 461, 1014, 1020,

1043, 1043A, 1043B, 1043C, 1136, 1160, 1161A, 1198A, 1207, 1224 1224A, 1230A, 1287, 1367, 1370, 1383, 1412,

1420, 1454 and 1464 DLM 4000.25

004010F867I5IA43 49 February 13, 2024

SE Transaction Set Trailer Pos: 30 Max: 1

Summary - 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 Rep

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 1

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 1