DLMS Implementation Convention (IC) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

004010F846R4RA28 1 January 22, 2024

846 Inventory Inquiry/Advice

Functional Group=IB

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Inventory Inquiry/Advice Transaction

Set (846) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used in the following ways:

(1) for a seller of goods and services to provide inventory information to a prospective purchaser, with no obligation to the purchaser to acquire

these goods or services; (2) for a representative of a seller of goods and services to supply inventory information to that seller; (3) for one

location to supply another location with inventory information; and (4) for an inquiry as to the availability of inventory with no obligation on the

seller of goods and services to reserve that inventory.

DLMS Note:

1a. Distribution centers and storage activities use this transaction set to transmit location reconciliation transactions to owners and

managers. Use one occurrence of this transaction set to transmit a single or multiple transactions. 

b. Distribution centers and storage activities use a single occurrence of this transaction set to transmit either location reconciliation request,

location reconciliation notification, or location reconciliation history notification transactions to one owner/manager. This transaction

encompasses the functionality of MILSTRAP Document Identifier Codes (DIC) DZH, DZN, DZP and NAVSUP P-724 BG1/BG2 serial/lot

number reporting transactions.

2. Legacy MILSTRAP functionality allows for Service and Agency data in various RP(s). Data Conveyed therein will require Service or

Agency identification to Defense Enterprise Data Standards Office (DEDSO) and incorporation into 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 DEDSO Web site at wwww.dla.mil/does/DLMS.

4. 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 required to accommodate Component- unique transaction requirements (e.g., B-series transactions). Data does not apply to legacy

MILSTRAP transactions.

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

5. This transaction may be used on a limited scope to provide item unique identification (IUID) information in accordance with DLMS

procedures and OSD Supply Policy. Loop ID REF (2/REF/390) documents the authorized uses of unique item identifier (UII) and serial

number. For all other purposes, IUID information is a placeholder for DLMS enhancements pending development of DLMS procedures and

overarching OSD Supply Policy. Refer to the IUID web at URL: http://www.acq.osd.mil/dpap/pdi/uid/ for DoD policy. 

6. This DLMS IC incorporates the Proposed DLMS Change and Approved DLMS Change (ADC) listed. PDC/ADCs are available from the

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

- ADC 45, Use of Both Ownership Code and Purpose Code in DLMS for Ammunition

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

- ADC 136, Revision to DLMS Supplement (DS) 846R Location Reconciliation Request to Support Commodity-Unique (Mapping Product)

Data and to Support MILSTRAP DZN/DZP functionality

- ADC 204, Revision to DS 846P and 846R to Support Requirements for Army Medical Material Agreement Inventory Records Management

Process (Supply)

- ADC 212, Revise DS 846R Location Reconciliation Request to Accommodate MILSTRAP DZH Consecutive Transaction Number

- ADC 230, Administrative Updates to DLMS Supplement (DS) 846R, Location Reconciliation Request (Supply)

- ADC 283, Migrate Navy Serial Number and Lot Number Transactions (NAVSUP P-724 BG1/BG2) to DLMS 846R Location Reconciliation

Request.

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

- ADC 307, Administrative Update to DLMS, Volume 2, Chapter 6, Physical Inventory Control and DLMS Supplements (DS) 846P, 846R, 

1a. Distribution centers and storage activities use this transaction set to transmit location reconciliation transactions to owners and

managers. Use one occurrence of this transaction set to transmit a single or multiple transactions. 

b. Distribution centers and storage activities use a single occurrence of this transaction set to transmit either location reconciliation request,

location reconciliation notification, or location reconciliation history notification transactions to one owner/manager. This transaction

encompasses the functionality of MILSTRAP Document Identifier Codes (DIC) DZH, DZN, DZP and NAVSUP P-724 BG1/BG2 serial/lot

number reporting transactions.

2. Legacy MILSTRAP functionality allows for Service and Agency data in various RP(s). Data Conveyed therein will require Service or

Agency identification to Defense Enterprise Data Standards Office (DEDSO) and incorporation into 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 DEDSO Web site at wwww.dla.mil/does/DLMS.

4. 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 required to accommodate Component- unique transaction requirements (e.g., B-series transactions). Data does not apply to legacy

MILSTRAP transactions.

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

5. This transaction may be used on a limited scope to provide item unique identification (IUID) information in accordance with DLMS

procedures and OSD Supply Policy. Loop ID REF (2/REF/390) documents the authorized uses of unique item identifier (UII) and serial

number. For all other purposes, IUID information is a placeholder for DLMS enhancements pending development of DLMS procedures and

overarching OSD Supply Policy. Refer to the IUID web at URL: http://www.acq.osd.mil/dpap/pdi/uid/ for DoD policy. 

6. This DLMS IC incorporates the Proposed DLMS Change and Approved DLMS Change (ADC) listed. PDC/ADCs are available from the

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

- ADC 45, Use of Both Ownership Code and Purpose Code in DLMS for Ammunition

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

- ADC 136, Revision to DLMS Supplement (DS) 846R Location Reconciliation Request to Support Commodity-Unique (Mapping Product)

Data and to Support MILSTRAP DZN/DZP functionality

- ADC 204, Revision to DS 846P and 846R to Support Requirements for Army Medical Material Agreement Inventory Records Management

Process (Supply)

- ADC 212, Revise DS 846R Location Reconciliation Request to Accommodate MILSTRAP DZH Consecutive Transaction Number

- ADC 230, Administrative Updates to DLMS Supplement (DS) 846R, Location Reconciliation Request (Supply)

- ADC 283, Migrate Navy Serial Number and Lot Number Transactions (NAVSUP P-724 BG1/BG2) to DLMS 846R Location Reconciliation

Request.

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

- ADC 307, Administrative Update to DLMS, Volume 2, Chapter 6, Physical Inventory Control and DLMS Supplements (DS) 846P, 846R, 
DLMS Implementation Convention (IC) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

004010F846R4RA28 2 January 22, 2024

and 888I (Supply/MILSTRAP)

- 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 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 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 441, Exception Rules to Accommodate Communication of Ammunition/Ammunition Related Quantities in Excess of Five Digits

(Supply/MILSTRIP/ MILSTRAP) (Supply)

- 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 470, Revise DLMS Supplement (DS) 846R, Location Reconciliation Request in Support of Reutilization Business Integration (RBI)

(Supply)

- ADC 1013, Intra-DLA Change: Disposal Turn In Document (DTID) Number Suffixing for DLMS 846C and 846R for use by DLA Disposition

Services Under Reutilization Business Integration (RBI) (Supply)

- ADC 1019, Small Arms/Light Weapons (SA/LW) Local Stock Number (LSN) Assignment for use by DLA Disposition Services in DLMS

527R, 846C, 846R, and 947I, under RBI (Supply)

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

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

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

- ADC 1198, Establishing Visibility of Capital Equipment for Service Owned Assets Stored at DLA Distribution Centers

- 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 1228, Revise DLMS 846P Physical Inventory Request and 846R Location Reconciliation Request to Enhance End of

Day/Reconciliation Process

- ADC 1230, Revise Balance Affecting Transactions to Authorize Air Force Contractor Inventory Control Points (CICP) use of Batch

Number, Serial Number, and Unique Item Identifier (UII) for Air Force Government Furnished Property (GFP) Accountability (GFP-A)

(Supply/Finance)

- ADC 1244, Establishing Visibility of Unique Item Tracking (UIT) Program Items for Service-Owned Assets Stored at DLA Distribution

Centers and Corresponding Revisions to Inventory Procedures Related to Capital Equipment

- 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 1318, Revise DLMS IC 846R Location Reconciliation Request Transaction to Add Project Code in Army Total Package Fielding (TPF)

Assets by Unit Materiel Fielding Points (UMFP)

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

November 13, 2018

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

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

Office (DEDSO) - Completed on March 4, 2022

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

Indicator to Wide Area Workflow

- ADC 1450, Administrative Update DLMS 846R Location Reconciliation Request Note_MFR

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

and 888I (Supply/MILSTRAP)

- 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 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 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 441, Exception Rules to Accommodate Communication of Ammunition/Ammunition Related Quantities in Excess of Five Digits

(Supply/MILSTRIP/ MILSTRAP) (Supply)

- 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 470, Revise DLMS Supplement (DS) 846R, Location Reconciliation Request in Support of Reutilization Business Integration (RBI)

(Supply)

- ADC 1013, Intra-DLA Change: Disposal Turn In Document (DTID) Number Suffixing for DLMS 846C and 846R for use by DLA Disposition

Services Under Reutilization Business Integration (RBI) (Supply)

- ADC 1019, Small Arms/Light Weapons (SA/LW) Local Stock Number (LSN) Assignment for use by DLA Disposition Services in DLMS

527R, 846C, 846R, and 947I, under RBI (Supply)

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

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

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

- ADC 1198, Establishing Visibility of Capital Equipment for Service Owned Assets Stored at DLA Distribution Centers

- 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 1228, Revise DLMS 846P Physical Inventory Request and 846R Location Reconciliation Request to Enhance End of

Day/Reconciliation Process

- ADC 1230, Revise Balance Affecting Transactions to Authorize Air Force Contractor Inventory Control Points (CICP) use of Batch

Number, Serial Number, and Unique Item Identifier (UII) for Air Force Government Furnished Property (GFP) Accountability (GFP-A)

(Supply/Finance)

- ADC 1244, Establishing Visibility of Unique Item Tracking (UIT) Program Items for Service-Owned Assets Stored at DLA Distribution

Centers and Corresponding Revisions to Inventory Procedures Related to Capital Equipment

- 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 1318, Revise DLMS IC 846R Location Reconciliation Request Transaction to Add Project Code in Army Total Package Fielding (TPF)

Assets by Unit Materiel Fielding Points (UMFP)

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

November 13, 2018

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

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

Office (DEDSO) - Completed on March 4, 2022

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

Indicator to Wide Area Workflow

- ADC 1450, Administrative Update DLMS 846R Location Reconciliation Request Note_MFR

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

Heading:

Pos Id Segment Name Req Max Use Repeat Notes Usage

010 ST Transaction Set Header M 1 Must use

020 BIA Beginning Segment for Inventory

Inquiry/Advice

M 1 Must use

* 040 CUR Currency O 1 Not Used

* 050 DTM Date/Time Reference O 10 Not Used

* 060 REF Reference Identification O 12 Not Used

* 070 PER Administrative Communications

Contact

O 3 Not Used

* 075 MEA Measurements O 20 Not Used

LOOP ID - N1 LOOP ID - N1 5

080 N1 Name O 1 Used

* 090 N2 Additional Name Information O 2 Not Used
DLMS Implementation Convention (IC) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

Pos Id Segment Name Req Max Use Repeat Notes Usage

004010F846R4RA28 3 January 22, 2024

* 100 N3 Address Information O 2 Not Used

* 110 N4 Geographic Location O 1 Not Used

* 120 REF Reference Identification O 12 Not Used

* 130 PER Administrative Communications

Contact

O 3 Not Used

LOOP ID - LM LOOP ID - LM 10

140 LM Code Source Information O 1 Used

150 LQ Industry Code M 100 Must use

Detail:

Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - LIN LOOP ID - LIN 10000

010 LIN Item Identification M 1 Must use

* 030 PID Product/Item Description O 200 Not Used

* 040 MEA Measurements O 40 Not Used

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

100 DTM Date/Time Reference O 10 Used

* 110 CTP Pricing Information O 25 Not Used

* 120 CUR Currency O 1 Not Used

* 130 SAC Service, Promotion, Allowance,

or Charge Information

O 25 Not Used

140 REF Reference Identification O >1 Used

* 150 PER Administrative Communications

Contact

O 3 Not Used

* 220 SDQ Destination Quantity O 500 Not Used

* 230 MAN Marks and Numbers O 1 Not Used

* 235 UIT Unit Detail O 5 Not Used

* 240 CS Contract Summary O 1 Not Used

* 250 DD Demand Detail O >1 Not Used

* 255 G53 Maintenance Type O 1 Not Used

* 256 PCT Percent Amounts O >1 Not Used

* 257 LDT Lead Time O 12 Not Used

LOOP ID - LM LOOP ID - LM 10

260 LM Code Source Information O 1 Used

270 LQ Industry Code M 100 Must use

* LOOP ID - SLN * LOOP ID - SLN 1000

* 280 SLN Subline Item Detail O 1 Not Used

290 PID Product/Item Description O 200 Used

300 MEA Measurements O 40 Used

310 PKG Marking, Packaging, Loading O 25 Used

LOOP ID - MAN LOOP ID - MAN 100

312 MAN Marks and Numbers O 1 Used

314 MEA Measurements O 40 Used

LOOP ID - QTY LOOP ID - QTY 99

320 QTY Quantity O 1 Used

* 330 UIT Unit Detail O 12 Not Used

* 340 MEA Measurements O 25 Not Used

* 350 LDT Lead Time O 12 Not Used

* 355 DTM Date/Time Reference O 10 Not Used

* LOOP ID - SCH * LOOP ID - SCH 25

* 360 SCH Line Item Schedule O 1 Not Used

370 MEA Measurements O 25 Used
DLMS Implementation Convention (IC) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

Pos Id Segment Name Req Max Use Repeat Notes Usage

004010F846R4RA28 4 January 22, 2024

LOOP ID - LM LOOP ID - LM >1

375 LM Code Source Information O 1 Used

376 LQ Industry Code M 100 Must use

LOOP ID - LS LOOP ID - LS 1

380 LS Loop Header O 1 Used

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

390 REF Reference Identification O 1 N2/390 Used

400 DTM Date/Time Reference O >1 Used

410 N1 Name O 1 Used

* LOOP ID - LM * LOOP ID - LM 10

* 420 LM Code Source Information O 1 Not Used

* 430 LQ Industry Code M 100 Not Used

440 LE Loop Trailer M 1 Must use

* LOOP ID - N1 * LOOP ID - N1 200

* 450 N1 Name O 1 Not Used

460 N2 Additional Name Information O 2 Used

470 N3 Address Information O 2 Used

480 N4 Geographic Location O 1 Used

490 REF Reference Identification O 12 Used

500 PER Administrative Communications

Contact

O 3 Used

Summary:

Pos Id Segment Name Req Max Use Repeat Notes Usage

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

020 SE Transaction Set Trailer M 1 Must use

Notes: 

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

2/390 The REF loop conveys serial number, lot number, and inventory data.

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

of the quantities (QTY02) of each QTY segment.
DLMS Implementation Convention (IC) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

004010F846R4RA28 5 January 22, 2024

ST Transaction Set Header Pos: 010 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).

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

846 Inventory Inquiry/Advice

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) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

004010F846R4RA28 6 January 22, 2024

BIA Beginning Segment for Inventory

Inquiry/Advice

Pos: 020 Max: 1

Heading - Mandatory

Loop: N/A Elements: 6

User Option (Usage): Must use

Purpose: To indicate the beginning of an Inventory Inquiry/Advice Transaction Set

Semantics: 

1. BIA03 identifies the number of the inquiry/advice that is transferred.

2. BIA04 identifies the date of the inquiry/advice that is transferred.

3. BIA05 identifies the time of the inquiry/advice that is transferred.

4. BIA03 identifies the number of the inquiry/advice that is transferred.

5. BIA04 identifies the date of the inquiry/advice that is transferred.

6. BIA05 identifies the time of the inquiry/advice that is transferred.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

BIA01 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 do not process as action

documents which affect accountable records.

ZZ Mutually Defined

DLMS Note:

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

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

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

BIA02 755 Report Type Code

Description: Code indicating the title or

contents of a document, report or

supporting item

M ID 2/2 Must use 1

Code Name

LC Location Inventory Report

DLMS Note:

Use to identify a Location Reconciliation Request Transaction. From distribution center/storage activity

to the owner/manger to reconcile storage activity and owner/manager records. (MILSTRAP DIC DZH

functionality.)

X4 Summary Report

DLMS Note:

Use to identify a Location Reconciliation Notification Transaction. Distribution center/storage activity

sends to owner/manager to advise of the number of Location Reconciliation Request transactions being

forwarded. (MILSTRAP DIC DZN functionality.)

ZZ Mutually Defined

DLMS Note:

Use to identify a Location Reconciliation History Notification Transaction. Distribution center/storage

activity sends to owner/manager to advise of the number of transaction history transactions being

forwarded. (MILSTRAP DIC DZP functionality.) An ANSI data maintenance was approved in version 
DLMS Implementation Convention (IC) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

Code Name

004010F846R4RA28 7 January 22, 2024

5030. The approved code/name is “LN-Location Reconciliation History Notification”.

BIA03 127 Reference Identification

Description: Reference information as

defined for a particular Transaction Set or

as specified by the Reference Identification

Qualifier

DLMS Note: Use Code "Z" for this data

element to satisfy mandatory X12 syntax

requirements.

M AN 1/30 Must use 1

BIA04 373 Date

Description: Date expressed as

CCYYMMDD

DLMS Note: 1. This is the date of the

transaction set preparation and

corresponds to the Universal Time

Coordinate (UTC).

2. Authorized DLMS enhancement; see

introductory DLMS note 4f on IC cover

page.

M DT 8/8 Must use 1

BIA05 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. This is the time of the

transaction set preparation and

corresponds to the Universal Time

Coordinate (UTC). Express time in a

four-position (HHMM) format, except for

CAV II. CAV II expresses time in an

eight-position Format (HHMMSSDD).

DLMS Note: 1. This is the time of the

transaction set preparation and

corresponds to the Universal Time

Coordinate (UTC). Express time in a

four-position (HHMM) format, except for

CAV II. CAV II expresses time in an

eight-position Format (HHMMSSDD).

2. Authorized DLMS enhancement; see

introductory DLMS note 4f on IC cover

page.

O TM 4/8 Used 1

BIA06 306 Action Code

Description: Code indicating type of action

DLMS Note: 1. Use to identify the type of

location reconciliation.

2. The following codes are authorized.

O ID 1/2 Used 1

Code Name

Z Mutually Defined

DLMS Note:

1. Use to identify that the transaction identified in BIA02 is associated with end-of-day processing.

2. An ANSI data maintenance was approved in version 5030. The approved code/name is “EO-End of

Day Processing”.

24 On-Hold

DLMS Note:

1. Use to identify that the transaction identified in BIA02 is associated with annual location

reconciliation.

2. An ANSI data maintenance was approved in version 5030. The approved code/name is “AN-Annual 
DLMS Implementation Convention (IC) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

Code Name

004010F846R4RA28 8 January 22, 2024

Location Reconciliation”.
DLMS Implementation Convention (IC) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

004010F846R4RA28 9 January 22, 2024

N1 Name Pos: 080 Max: 1

Heading - Optional

Loop: N1 Elements: 4

User Option (Usage): Used

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

Syntax Rules: 

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

2. R0203 - At least one of N102 or N103 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.

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

4. 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 and receiving the transaction set.

2. Must use at least one iteration of this N1 segment to identify the organization to receive the transaction (N106 code TO with appropriate

N101 code). May 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: 1. Use only one of codes KA

or OW.

2. The following codes are authorized.

M ID 2/3 Must use 1

Code Name

KA Item Manager

DLMS Note:

Use to identify the Integrated Material Manager (IMM) for the materiel reported.

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.

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

OW Owner of Property or Unit

DLMS Note:

1. Use to identify the owner of the property reported.

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

1. Use to identify the owner of the property reported.

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

SB Storage Area

DLMS Note:

1. Must use to identify the depot or storage activity.
DLMS Implementation Convention (IC) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

Code Name

004010F846R4RA28 10 January 22, 2024

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

Code Name

10 Department of Defense Activity Address Code (DODAAC)

DLMS Note:

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

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

by DODAAC.

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 Used 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 with 1/N101/080 code SB to indicate the organization cited in N104 is originating the

transaction set.

TO Message To

DLMS Note:

Must use with the 1/N101/080 codes KA or OW to indicate the organization cited in 1/N104/080 is

receiving the transaction set.
DLMS Implementation Convention (IC) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

004010F846R4RA28 11 January 22, 2024

LM Code Source Information Pos: 140 Max: 1

Heading - Optional

Loop: LM Elements: 1

User Option (Usage): Used

Purpose: To transmit standard code list identification information

Comments: 

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

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

DLMS Note:

Must use this 1/LM/140 loop to identify coded information maintained in department 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) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

004010F846R4RA28 12 January 22, 2024

LQ Industry Code Pos: 150 Max: 100

Heading - Mandatory

Loop: LM Elements: 2

User Option (Usage): Must use

Purpose: Code to transmit standard industry codes

Syntax Rules: 

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

DLMS Note:

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LQ01 1270 Code List Qualifier Code

Description: Code identifying a specific

industry code list

DLMS Note: The following codes are

authorized.

O ID 1/3 Used 1

Code Name

0 Document Identification Code

DLMS Note:

1. Future Streamlined data; see introductory DLMS note 4c.

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

3. In a mixed DLSS-DLMS environment, when including BG1/BG2 data for Inter-Service Ammunition

interface, must use 2 iterations of LQ to provide DIC DZH 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).

1. Future Streamlined data; see introductory DLMS note 4c.

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

3. In a mixed DLSS-DLMS environment, when including BG1/BG2 data for Inter-Service Ammunition

interface, must use 2 iterations of LQ to provide DIC DZH 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).

A9 Supplemental Data

DLMS Note:

1. Use to identify supplemental address/data.

2. Future streamlined data; see introductory DLMS note 4c.

AJ Utilization Code

DLMS Note:

1. Under DLSS, this is the first position of the document serial number.

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

LQ02 1271 Industry Code

Description: Code indicating a code from a

specific industry code list

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

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

004010F846R4RA28 13 January 22, 2024

LIN Item Identification Pos: 010 Max: 1

Detail - Mandatory

Loop: LIN Elements: 5

User Option (Usage): Must use

Purpose: To specify basic item identification data

Syntax Rules: 

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Semantics: 

1. LIN01 is the line item identification

2. LIN01 is the line item identification

Comments: 

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

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

ISBN No., Model No., or SKU.

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

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

ISBN No., Model No., or SKU.

DLMS Note:

Must use the 2/LIN/010 loop to identify the materiel, transaction number, and inventory information associated with the transaction.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LIN01 350 Assigned Identification

Description: Alphanumeric characters

assigned for differentiation within a

transaction set

DLMS Note: Use to identify the count of

location reconciliation transactions. In the

first 2/LIN/010 loop iteration, cite the

numeric 1. In each subsequent loop

iteration, increase incrementally by one.

DLMS Note: Use to identify the count of

location reconciliation transactions. In the

first 2/LIN/010 loop iteration, cite the

numeric 1. In each subsequent loop

iteration, increase incrementally by one.

O AN 1/20 Used 1

LIN02 235 Product/Service ID Qualifier

Description: Code identifying the

type/source of the descriptive number used

in Product/Service ID (234)

DLMS Note: 1. For 1/BIA02/020 code LC,

use only one of codes A2, A3, A4, FB, FS,

MG, SW, YP, ZR or ZZ to identify the item

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

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F846R4RA28 14 January 22, 2024

of inventory. Must use National Stock

Number (NSN) when known 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 or

Material Control Tracking (MCT) Tag

Number.

of inventory. Must use National Stock

Number (NSN) when known 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 or

Material Control Tracking (MCT) Tag

Number.

2. For 1/BIA02/020 codes X4 and ZZ, only

use LIN02 code ZZ.

3. The following codes are authorized.

Code Name

A2 Department of Defense Identification Code (DoDIC)

DLMS Note:

1. Use to identify ammunition items.

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

A3 Locally Assigned Control Number

DLMS Note:

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

(TEWLS) use to cite their Local Catalog Identification which can reference multiple prime vendor part

numbers for a specific site.

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

A4 Subsistence Identification Number

DLMS Note:

Use to identify subsistence items.

F4 Series Identifier

DLMS Note:

1. Use to identify the manufacturer's series number of the end item.

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

FB Form Number

DLMS Note:

1. Use to identify the form stock number.

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

FS National Stock Number

MG Manufacturer's Part Number

DLMS Note:

Use to identify nonstandard materiel.

MN Model Number

DLMS Note:

1. Use to identify the manufacturer's model number of the end item.

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

SN Serial Number

DLMS Note:

1. Use to identify the manufacturer's serial number of the end item.

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

SW 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 
DLMS Implementation Convention (IC) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

Code Name

004010F846R4RA28 15 January 22, 2024

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.

YP Publication Number

DLMS Note:

1. Use to identify the publication stock number. 

2. DLMS enhancement, see introductory DLMS note 4a.

ZR Service Control Identification

DLMS Note:

Use to identify Materiel Control Tracking (MCT) tag number. The MCT tag number is an authorized

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

ZZ Mutually Defined

DLMS Note:

1. For 1/BIA02/20 code LC (Location Reconciliation Request), 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.

2. For Location Reconciliation Request transactions, use when a management control number (MCN) is

provided. This includes the MCN assigned by the DoD small arms/light weapons (SA/LW) Registry for

the DoD SA/LW Serialization Program, IAW DLM 4000.25, DLMS, Volume 2.

3. For 1/BIA02/20 codes X4 (Location Reconciliation Notification) and ZZ (Location Reconciliation

History Notification), must use to comply with ANSI syntax requirements. Indicate ZZ in LIN03.

1. For 1/BIA02/20 code LC (Location Reconciliation Request), 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.

2. For Location Reconciliation Request transactions, use when a management control number (MCN) is

provided. This includes the MCN assigned by the DoD small arms/light weapons (SA/LW) Registry for

the DoD SA/LW Serialization Program, IAW DLM 4000.25, DLMS, Volume 2.

3. For 1/BIA02/20 codes X4 (Location Reconciliation Notification) and ZZ (Location Reconciliation

History Notification), must use to comply with ANSI syntax requirements. Indicate ZZ in LIN03.

LIN03 234 Product/Service ID

Description: Identifying number for a

product or service

M AN 1/48 Must use 1

LIN04 235 Product/Service ID Qualifier

Description: Code identifying the

type/source of the descriptive number used

in Product/Service ID (234)

X ID 2/2 Used 1

Code Name

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

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

3. DLA Disposition Services uses with Location Reconciliation Request transactions, for confiscated or

captured foreign weapons, to identify the disposition LSN in addition to the SA/LW MCN cited in

LIN02/LIN03 by qualifier ZZ. Authorized DLMS enhancement for DLA Disposition Services. DLA

Disposition Services requires the disposition LSN for internal DLA processing only. Refer to ADC 1019.

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.

3. DLA Disposition Services uses with Location Reconciliation Request transactions, for confiscated or

captured foreign weapons, to identify the disposition LSN in addition to the SA/LW MCN cited in

LIN02/LIN03 by qualifier ZZ. Authorized DLMS enhancement for DLA Disposition Services. DLA

Disposition Services requires the disposition LSN for internal DLA processing only. Refer to ADC 1019.

ZB Commercial and Government Entity (CAGE) Code

DLMS Note:
DLMS Implementation Convention (IC) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

Code Name

004010F846R4RA28 16 January 22, 2024

Use with LIN02 code MG to uniquely identify a manufacturer's part number.

LIN05 234 Product/Service ID

Description: Identifying number for a

product or service

X AN 1/48 Used 1
DLMS Implementation Convention (IC) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

004010F846R4RA28 17 January 22, 2024

DTM Date/Time Reference Pos: 100 Max: 10

Detail - Optional

Loop: LIN Elements: 3

User Option (Usage): Used

Purpose: To specify pertinent dates and times

Syntax Rules: 

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

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

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

DLMS Note:

Must use 2/DTM/100 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

M ID 3/3 Must use 1

Code Name

097 Transaction Creation

DLMS Note:

1. Use to identify the date the transaction was prepared.

2. Authorized DLMS enhancement; see introductory DLMS note 4f. on IC cover page.

152 Effective Date of Change

DLMS Note:

Use in DLA DDMA location reconciliation requests to identify the cyclical map product effective date. 

Each DLA DDMA location reconciliation request should include either an edition date (used in

conjunction with 2/REF01/040 edition number) or a map effective date, but not both.

171 Revision

DLMS Note:

Use in DLA DDMA location reconciliation requests to identify the map edition date. Each DLA DDMA

location reconciliation request should include either an edition date (used in conjunction with

2/REF01/140 edition number) or a product effective date, but not both.

600 As Of

DLMS Note:

Must use to identify the close of business date (e.g., mutually agreed upon cutoff date) associated with

the location reconciliation.

DTM02 373 Date

Description: Date expressed as

CCYYMMDD

DLMS Note: DLMS enhancement; see

introductory DLMS note 4a.

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 097

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

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F846R4RA28 18 January 22, 2024

(Transaction Creation) to provide the time

associated with preparation of the physical

inventory request.

2. Express time in UTC using a

four-position (HHMM) format.

3. Authorized DLMS enhancement; see

introductory DLMS note 4f. on IC cover

page.
DLMS Implementation Convention (IC) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

004010F846R4RA28 19 January 22, 2024

REF Reference Identification Pos: 140 Max: >1

Detail - Optional

Loop: LIN Elements: 3

User Option (Usage): Used

Purpose: To specify identifying information

Syntax Rules: 

1. R0203 - At least one of REF02 or REF03 is required.

Semantics: 

1. REF04 contains data relating to the value cited in REF02.

2. REF04 contains data relating to the value cited in REF02.

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: The following code is

authorized.

M ID 2/3 Must use 1

Code Name

6G Map Number

DLMS Note:

Use in DLA map location reconciliation requests to identify the map edition number. Component unique

enhancement.

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

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

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 4e. 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 4e. on IC cover page. Refer to ADC

1224.

FJ Line Item Control Number

DLMS Note:

Used in a mixed DLSS/DLMS environment to provide the information conveyed by MILSTRAP DIC

DZH, rp 60-66 ‘consecutive transaction number’. This is a consecutive number, beginning with 1 in the

first transaction, to identify each transaction in the reconciliation. Used when each 846R is limited to

being the equivalent of a single MILSTRAP DZH location reconciliation request. Future streamlined

data; see introductory DLMS note 4c. See ADC 212.

TN Transaction Reference Number

DLMS Note:

1. Use to identify the document number.
DLMS Implementation Convention (IC) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

Code Name

004010F846R4RA28 20 January 22, 2024

2. For Disposition Services, use to provide the Disposal Turn-In Document (DTID) Number. 

3. For other than DLA Disposition Services, use of the document number with location reconciliation

transactions, is a DLMS enhancement and procedures for use must be developed. See introductory

DLMS note 4a. 

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

REF04 C040 Reference Identifier

Description: To identify one or more

reference numbers or identification

numbers as specified by the Reference

Qualifier

O Comp Used 1

REF04-01 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

DLMS Note: The following codes are

authorized.

M ID 2/3 Must use 1

Code Name

W8 Suffix

DLMS Note:

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

2. Disposition Services uses to provide the DTID number suffix, when applicable, with Location

Reconciliation Request transactions (1/BIA02/20 Report Type Code LC) and Location Reconciliation

Notification transactions (1/BIA02/20 Report Type Code X4). 

3. For other than DLA Disposition Services, use of document number suffix with location reconciliation

transactions is a DLMS enhancement and procedures for use must be developed. See introductory

DLMS note 4a.

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

2. Disposition Services uses to provide the DTID number suffix, when applicable, with Location

Reconciliation Request transactions (1/BIA02/20 Report Type Code LC) and Location Reconciliation

Notification transactions (1/BIA02/20 Report Type Code X4). 

3. For other than DLA Disposition Services, use of document number suffix with location reconciliation

transactions is a DLMS enhancement and procedures for use must be developed. See introductory

DLMS note 4a.

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) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

004010F846R4RA28 21 January 22, 2024

LM Code Source Information Pos: 260 Max: 1

Detail - Optional

Loop: LM Elements: 1

User Option (Usage): Used

Purpose: To transmit standard code list identification information

Comments: 

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

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

DLMS Note:

Use this 2/LM/260 loop to identify coded information maintained in department 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) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

004010F846R4RA28 22 January 22, 2024

LQ Industry Code Pos: 270 Max: 100

Detail - Mandatory

Loop: LM Elements: 2

User Option (Usage): Must use

Purpose: Code to transmit standard industry codes

Syntax Rules: 

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

DLMS Note:

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LQ01 1270 Code List Qualifier Code

Description: Code identifying a specific

industry code list

DLMS Note: The following codes are

authorized.

O ID 1/3 Used 1

Code Name

A9 Supplemental Data

DLMS Note:

1. Use to identify supplemental address/data.

2. Future streamlined data; see introductory DLMS note 4c.

AJ Utilization Code

DLMS Note:

1. Under DLSS, this is the first position of the document serial number.

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

EQ Controlled Inventory Item Code

DLMS Note:

Use to identify the controlled inventory item code associated with the reported materiel.

FD Demilitarization Code

DLMS Note:

Authorized DLMS enhancement for use by DLA Disposition Services only. Refer to ADC 470.

FE Shelf Life Code

DLMS Note:

Use to identify the shelf-life code associated with the reported materiel.

FH Type of Location Reconciliation Request

DLMS Note:

Data to be removed from transaction in future version. The type of location reconciliation (annual or

end-of-day) should be conveyed by 1/BIA06/020.

SRC List of codes identifying DoD Serialized Report Type Code

DLMS Note:

1. The Air Force code 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. This is

the Air Force Serialized Report Code. Refer to ADC 1230.

2. Migration code SRC is established for use in the 846R, 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/270:

1. The Air Force code 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. This is

the Air Force Serialized Report Code. Refer to ADC 1230.

2. Migration code SRC is established for use in the 846R, 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/270:
DLMS Implementation Convention (IC) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

Code Name

004010F846R4RA28 23 January 22, 2024

A Small Arms

C Communications Security (COMSEC)

D Reserved

R Nuclear Weapons Related Material (NWRM) COMSEC

W NWRM

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) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

004010F846R4RA28 24 January 22, 2024

QTY Quantity Pos: 320 Max: 1

Detail - Optional

Loop: QTY Elements: 3

User Option (Usage): Used

Purpose: To specify quantity information

Syntax Rules: 

1. E0204 - Only one of QTY02 or QTY04 may be present.

2. R0204 - At least one of QTY02 or QTY04 is required.

Semantics: 

1. QTY04 is used when the quantity is non-numeric.

2. QTY04 is used when the quantity is non-numeric.

DLMS Note:

1. Use multiple iterations of the 2/QTY/320 loop to stratify the on hand quantity by materiel classification.

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

QTY01 673 Quantity Qualifier

Description: Code specifying the type of

quantity

M ID 2/2 Must use 1

Code Name

17 Quantity on Hand

DLMS Note:

Use to identify custodial record balance.

46 Total transactions

DLMS Note:

Must use with location reconciliation notification transactions (1/BIA02/020 codes X4 and ZZ) to indicate

the number of history or location reconciliation request transactions submitted.

IQ In-Transit Quantity

DLMS Note:

1. Use for Air Force GFP accountability to identify the GFP Intransit Quantity. This is the total quantity

of confirmed shipments (Materiel/ Disposal Release Confirmation) without a matching receipt

acknowledgment from the receiving activity excluding property issued for local disposal, internal USAF

CICP deliveries, and customer pick-up. The USAF GFP APSR retains no owner property records for

property issued under these exclusions; therefor tracking is not required. See ADC 1228.

2. DLMS enhancement. See Introductory DLMS Note 4a in the IC cover page.

1. Use for Air Force GFP accountability to identify the GFP Intransit Quantity. This is the total quantity

of confirmed shipments (Materiel/ Disposal Release Confirmation) without a matching receipt

acknowledgment from the receiving activity excluding property issued for local disposal, internal USAF

CICP deliveries, and customer pick-up. The USAF GFP APSR retains no owner property records for

property issued under these exclusions; therefor tracking is not required. See ADC 1228.

2. DLMS enhancement. See Introductory DLMS Note 4a in the IC cover page.

QTY02 380 Quantity

Description: Numeric value of quantity

DLMS Note: 1. Express as a whole

number with no decimals.

2. Quantity field size in the Location

Reconciliation Request Transaction is 10

positions. Corresponding MILSTRAP DZH

transaction provides for a 10 position

quantity field.

X R 1/15 Used 1

QTY03 C001 Composite Unit of Measure

Description: To identify a composite unit of

measure(See Figures Appendix for

examples of use)

O Comp Used 1
DLMS Implementation Convention (IC) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F846R4RA28 25 January 22, 2024

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

taken

DLMS Note: DLMS users see the Unit of

Issue and Purchase Unit Conversion Table

for available codes.

All valid standard codes are used.

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

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

004010F846R4RA28 26 January 22, 2024

LM Code Source Information Pos: 375 Max: 1

Detail - Optional

Loop: LM Elements: 1

User Option (Usage): Used

Purpose: To transmit standard code list identification information

Comments: 

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

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

DLMS Note:

Use this 2/LM/375 loop to identify coded information maintained in department 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) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

004010F846R4RA28 27 January 22, 2024

LQ Industry Code Pos: 376 Max: 100

Detail - Mandatory

Loop: LM Elements: 2

User Option (Usage): Must use

Purpose: Code to transmit standard industry codes

Syntax Rules: 

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

DLMS Note:

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage 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

4a).

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

4a).

2. The following codes are authorized.

O ID 1/3 Used 1

Code Name

78 Project Code

DLMS Note:

Use to identify the project code when stocks are segregated at DLA DSS Unit Materiel Fielding Points

(UMFP) and GCSS Army (Fielding Site) Total Package Fielding locations. Refer to ADC 1318.

83 Supply Condition Code

87 Subsistence Type of Pack Code

DLMS Note:

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

99 Purpose Code

DLMS Note:

Use when assets are segregated physically or on storage activity records by purpose code.

A1 Ownership Code

DLMS Note:

Use when assets are segregated physically or on storage activity records by ownership code.

A9 Supplemental Data

DLMS Note:

1. Use to identify supplemental address/data.

2. Future streamlined data; see introductory DLMS note 4c.

AJ Utilization Code

DLMS Note:

1. Under DLSS, this is the first position of the document serial number.

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

GQ Group Qualifier Code

DLMS Note:

Use to identify the Materiel Management Aggregation Code (MMAC) for NSNs to be managed by a

specific manager (i.e., system, program, aggregation, selected FSC, technology group). This is an Air

Force-unique data element, meaningful to the Air Force only. Non-Air Force Components perpetuate 
DLMS Implementation Convention (IC) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

Code Name

004010F846R4RA28 28 January 22, 2024

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.

COG Cognizance Symbol

DLMS Note:

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.

IMC Item Management Code

DLMS Note:

Use to identify the Item Management Code (IMC) for integrated material management. This is a

Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without

action.

MCC Material Control Code

DLMS Note:

Use to identify the Material Control Code (MCC) for special inventory reporting. This is a Navy-unique

data element meaningful to Navy only; Non-Navy Components are to perpetuate without action.

SMI Special Material Identification Code

DLMS Note:

Use to identify the Special Material Identification Code (SMIC) for an end item. This is a Navy-unique

data element meaningful to Navy only; Non-Navy Components are to perpetuate without action.

LQ02 1271 Industry Code

Description: Code indicating a code from a

specific industry code list

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

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

004010F846R4RA28 29 January 22, 2024

LS Loop Header Pos: 380 Max: 1

Detail - Optional

Loop: LS Elements: 1

User Option (Usage): Used

Purpose: To indicate that the next segment begins a loop

Semantics: 

1. One loop may be nested contained within another loop, provided the inner nested loop terminates before the outer loop. When specified

by the standard setting body as mandatory, this segment in combination with "LE", must be used. It is not to be used if not specifically

set forth for use. The loop identifier in the loop header and trailer must be identical. The value for the identifier is the loop ID of the

required loop segment. The loop ID number is given on the transaction set diagram in the appropriate ASC X12 version/release.

2. One loop may be nested contained within another loop, provided the inner nested loop terminates before the outer loop. When specified

by the standard setting body as mandatory, this segment in combination with "LE", must be used. It is not to be used if not specifically

set forth for use. The loop identifier in the loop header and trailer must be identical. The value for the identifier is the loop ID of the

required loop segment. The loop ID number is given on the transaction set diagram in the appropriate ASC X12 version/release.

Comments: 

1. See Figures Appendix for an explanation of the use of the LS and LE segments.

2. See Figures Appendix for an explanation of the use of the LS and LE segments.

DLMS Note:

Use as needed in each 2/QTY/320 loop to prevent a syntax error in the use of the 2/REF/390 loop.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LS01 447 Loop Identifier Code

Description: The loop ID number given on

the transaction set diagram is the value for

this data element in segments LS and LE

DLMS Note: Cite REF to indicate the

2/REF/390 loop.

M AN 1/6 Must use 1
DLMS Implementation Convention (IC) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

004010F846R4RA28 30 January 22, 2024

REF Reference Identification Pos: 390 Max: 1

Detail - Optional

Loop: REF 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.

2. REF04 contains data relating to the value cited in REF02.

DLMS Note:

1. The entire 2/REF/390 loop is an authorized DLMS enhancement for use to provide item unique identification (IUID) serialized data as

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

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

number when applicable. Must use 2/REF/390 loop in location reconciliation request transactions when authorized for including UII, serial

number, and/or batch/lot number.

3. Repeat the 2/REF/390 loop for each item to be identified by UII, serial number or batch/lot number. If UII and serial number, and/or

batch/lot number are required for the item, enter the UII in REF01, and enter the serial number and/or batch/lot number in REF04. If UII is

not used, enter the serial number in REF01 and enter the batch/lot number in REF04. If only batch/lot number is required, enter the batch/lot

number in REF01.

4. Authorized for use with location reconciliation request transactions to support Service Ammunition systems (i.e., Naval Operational

Logistics Support Center (NOLSC) Ordnance Information System – Wholesale (OIS-W) requirement; 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). See introductory DLMS notes 4a and 4e. Refer to ADC 283 and ADC 445.

5. Authorized in support of Financial Improvement and Audit Readiness (FIAR) compliance for capital equipment. Capital candidates require

serialization data visibility. Prepare location reconciliation request transactions with the serial number as mandatory and when available,

include the UII. Refer to ADC 1198.

6. Authorized under DOD IUID policy for UIT programs. UIT programs require serialization data visibility. For all UIT programs with the

exception of SA/LW, prepare the location reconciliation request with the serial number and when available, include the UII. For SA/LW,

refer to the separate program procedures pending transition to DLMS logistics transactions. Refer to ADC 1244.

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

systems. Authorized for use with serial number, UII, and batch/lot number. Refer to ADC 1230. 

8. Supports Inter-Service Ammunition BG1/BG2 data requirement. See introductory DLMS note 4e. When the serial number is used in

REF01 with Ammunition BG1/BG2 transactions, this qualifier implies that the transaction is a BG1 (Serial Number or Lot and Serial Number

Controlled Item Transaction). When the batch number is used in REF01 with Ammunition BG1/BG2 transactions, this qualifier implies that

the transaction is a BG2 (Lot Number Controlled Item Transaction). In a mixed DLSS/DLMS environment, UII is not used in Ammunition

BG1/BG2 transactions. Only authorized values for Ammunition BG1/BG2 are BT and SE, used at REF01 and REF04-01. Refer to ADC 283

and ADC 445.

1. The entire 2/REF/390 loop is an authorized DLMS enhancement for use to provide item unique identification (IUID) serialized data as

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

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

number when applicable. Must use 2/REF/390 loop in location reconciliation request transactions when authorized for including UII, serial

number, and/or batch/lot number.

3. Repeat the 2/REF/390 loop for each item to be identified by UII, serial number or batch/lot number. If UII and serial number, and/or

batch/lot number are required for the item, enter the UII in REF01, and enter the serial number and/or batch/lot number in REF04. If UII is

not used, enter the serial number in REF01 and enter the batch/lot number in REF04. If only batch/lot number is required, enter the batch/lot

number in REF01.

4. Authorized for use with location reconciliation request transactions to support Service Ammunition systems (i.e., Naval Operational

Logistics Support Center (NOLSC) Ordnance Information System – Wholesale (OIS-W) requirement; 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). See introductory DLMS notes 4a and 4e. Refer to ADC 283 and ADC 445.

5. Authorized in support of Financial Improvement and Audit Readiness (FIAR) compliance for capital equipment. Capital candidates require

serialization data visibility. Prepare location reconciliation request transactions with the serial number as mandatory and when available,

include the UII. Refer to ADC 1198.

6. Authorized under DOD IUID policy for UIT programs. UIT programs require serialization data visibility. For all UIT programs with the

exception of SA/LW, prepare the location reconciliation request with the serial number and when available, include the UII. For SA/LW,

refer to the separate program procedures pending transition to DLMS logistics transactions. Refer to ADC 1244.

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

systems. Authorized for use with serial number, UII, and batch/lot number. Refer to ADC 1230. 

8. Supports Inter-Service Ammunition BG1/BG2 data requirement. See introductory DLMS note 4e. When the serial number is used in

REF01 with Ammunition BG1/BG2 transactions, this qualifier implies that the transaction is a BG1 (Serial Number or Lot and Serial Number

Controlled Item Transaction). When the batch number is used in REF01 with Ammunition BG1/BG2 transactions, this qualifier implies that

the transaction is a BG2 (Lot Number Controlled Item Transaction). In a mixed DLSS/DLMS environment, UII is not used in Ammunition

BG1/BG2 transactions. Only authorized values for Ammunition BG1/BG2 are BT and SE, used at REF01 and REF04-01. Refer to ADC 283

and ADC 445.

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: The following codes are

authorized.

M ID 2/3 Must use 1

Code Name

BT Batch Number

DLMS Note:

Use to identify the manufacturer's batch/lot number or other number identifying the production run when

UII and/or serial number are not required. If UII and/or serial number are required in addition to the 
DLMS Implementation Convention (IC) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

Code Name

004010F846R4RA28 31 January 22, 2024

batch/lot number, enter the batch/lot number in REF04. 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 when UII is not required. If UII is required in addition to the serial

number, enter serial number in REF04. The serial number may not exceed 30 characters and may only

include alpha numeric characters, dashes and forward slashes. Spaces are not allowed.

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. An ANSI data maintenance was approved in version 5020. The approved

code/name is “UII-Department of Defense Unique Item Identifier”.

2. See DLMS introductory DLMS note 4f.

REF02 127 Reference Identification

Description: Reference information as

defined for a particular Transaction Set or

as specified by the Reference Identification

Qualifier

DLMS Note: For use with REF01 codes BT

and SE.

X AN 1/30 Used 1

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

O Comp Used 1

REF04-01 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

DLMS Note: The following codes are

authorized.

M ID 2/3 Must use 1

Code Name

BT Batch Number

DLMS Note:

Use to identify the manufacturer's batch/lot number or other number identifying the production run,

when UII or serial number is entered in REF01, and batch/lot is the only other identifying number in

2/REF/390. 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 when UII is entered in REF01 and serial number is also used. The

serial number may not exceed 30 characters and may only include alpha numeric characters, dashes

and forward slashes. Spaces are not allowed.

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) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F846R4RA28 32 January 22, 2024

REF04-03 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

DLMS Note: The following codes are

authorized.

X ID 2/3 Used 1

Code Name

0N Attached To

DLMS Note:

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

Size for the lot number identified in REF02. Supports Ammunition DIC BG1/BG2, rp 25-29. See

introductory DLMS note 4.e. Refer to ADC 283 and ADC 445.

BT Batch Number

DLMS Note:

Use to identify the manufacturer's batch/lot number or other number identifying the production run when

UII is entered in REF01 and serial number is entered in REF04-01. The batch/lot number may not

exceed 20 characters in accordance with IUID policy. 

REF04-04 127 Reference Identification

Description: Reference information as

defined for a particular Transaction Set or

as specified by the Reference Identification

Qualifier

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

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

004010F846R4RA28 33 January 22, 2024

DTM Date/Time Reference Pos: 400 Max: >1

Detail - Optional

Loop: REF Elements: 2

User Option (Usage): Used

Purpose: To specify pertinent dates and times

Syntax Rules: 

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

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

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

DLMS Note:

Use multiple repetitions as needed to identify dates related to data represented 2/REF/390.

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

DLMS note 4e. Refer to ADC 283 and ADC 445.

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 DLMS note 4e. Refer to ADC 283 and ADC 445.

DTM02 373 Date

Description: Date expressed as

CCYYMMDD

X DT 8/8 Used 1
DLMS Implementation Convention (IC) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

004010F846R4RA28 34 January 22, 2024

N1 Name Pos: 410 Max: 1

Detail - Optional

Loop: REF Elements: 3

User Option (Usage): Used

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

Syntax Rules: 

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

2. R0203 - At least one of N102 or N103 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: The following codes are

authorized.

M ID 2/3 Must use 1

Code Name

MF Manufacturer of Goods

N103 66 Identification Code Qualifier

Description: Code designating the

system/method of code structure used for

Identification Code (67)

DLMS Note: The following codes are

authorized.

X ID 1/2 Used 1

Code Name

33 Commercial and Government Entity (CAGE)

N104 67 Identification Code

Description: Code identifying a party or

other code

X AN 2/80 Used 1
DLMS Implementation Convention (IC) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

004010F846R4RA28 35 January 22, 2024

LE Loop Trailer Pos: 440 Max: 1

Detail - Mandatory

Loop: LS Elements: 1

User Option (Usage): Must use

Purpose: To indicate that the loop immediately preceding this segment is complete

Semantics: 

1. One loop may be nested contained within another loop, provided the inner nested loop terminates before the other loop. When specified

by the standards setting body as mandatory, this segment in combination with "LS", must be used. It is not to be used if not specifically

set forth for use. The loop identifier in the loop header and trailer must be identical. The value for the identifier is the loop ID of the

required loop beginning segment. The loop ID number is given on the transaction set diagram in the appropriate ASC X12

version/release.

2. One loop may be nested contained within another loop, provided the inner nested loop terminates before the other loop. When specified

by the standards setting body as mandatory, this segment in combination with "LS", must be used. It is not to be used if not specifically

set forth for use. The loop identifier in the loop header and trailer must be identical. The value for the identifier is the loop ID of the

required loop beginning segment. The loop ID number is given on the transaction set diagram in the appropriate ASC X12

version/release.

Comments: 

1. See Figures Appendix for an explanation of the use of the LE and LS segments.

2. See Figures Appendix for an explanation of the use of the LE and LS segments.

DLMS Note:

Use in each 2/QTY/320 loop to terminate any 2/REF/390 loop iterations.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LE01 447 Loop Identifier Code

Description: The loop ID number given on

the transaction set diagram is the value for

this data element in segments LS and LE

DLMS Note: Repeat the content of

2/LS/380

M AN 1/6 Must use 1
DLMS Implementation Convention (IC) 846R,

Location Reconciliation Request

ADC 45, 77, 136, 204, 212, 230, 283, 295, 307, 381, 381A, 436, 441, 445, 470, 1013, 1019, 1043C, 1136,

1198, 1224, 1224A, 1228, 1230, 1244, 1287, 1318, 1367, 1412, 1450 and 1454 DLM 4000.25

004010F846R4RA28 36 January 22, 2024

SE Transaction Set Trailer Pos: 020 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