DLMS Implementation Convention (IC) 846P

Physical Inventory Request

ADC 45, 77, 134, 138, 164, 198, 204, 270, 295, 307, 320, 381, 381A, 393, 436, 1043C, 1224, 1224A, 1228,

1244, 1254, 1287, 1349, 1367, 1412 and 1454 DLM 4000.25

004010F846P4PA23 1 August 21, 2023

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:

1. This transaction is used to request, inquire about, and cancel a physical inventory, and to request transaction history. Use one occurrence

of this transaction set to transmit a single or multiple transactions.

a. Owners and managers use this transaction set to request, inquire about, and cancel a physical inventory by a distribution center or

storage activity. Owners and managers also use this transaction set to request transaction history. Distribution depots/storage activities use

this transaction set to cancel and/or reschedule a physical inventory request by an owner/manager. Distribution depots/storage activities

also use this transaction set to respond to a request for transaction history when no history is available and an inquiry about a request for a

physical inventory. Distribution depots/storage activities also use this transaction set to provide the owner/manager End of Day processing

transactions count information. This transaction encompasses the functionality of MILSTRAP Document Identifier Codes (DIC) DJA, DZJ,

DZK when rp 30-43 is 8-filled or 9-filled, and DZM. This transaction also accommodates the functionality of non-DLSS Navy DIC BZA and

BZC.

2. Use a single occurrence of this transaction set to exchange transactions between a single owner/manager and a single or multiple

distribution depots/storage activities, or between a single distribution depot/storage activity and a single or multiple owners/managers. For

use as an end of day transaction count, depot/storage activity sends a single occurrence of this transaction to a single owner/manager.

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

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

4. This DLMS Implementation Convention (IC) 846P 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 field 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 DLSS

transactions.

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

of the ANSI X12 standard, such data is not compatible with DLSS/DLMS conversion and may not be supported by the recipient's automated

processing system. Components must coordinate implementation of enhanced capability with DEDSO prior to use.

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

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

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

inappropriate rejection of the transaction.

5. This DLMS IC incorporates the Proposed DLMS Change (PDC) and Approved DLMS Change (ADC) listed. PDCs/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 134, Revision to DS 846P, Physical Inventory Request to Add Physical Inventory Cutoff Date (Supply)

- ADC 138, Revisions to DLMS Supplement (DS) 846P, Physical Inventory Request, to Capture Impact of Approved DLMS Change (ADC)

33, and Other Administrative Changes

- ADC 164, Revision to DLMS Supplement 846P, Physical Inventory Request, to Accommodate Functionality of End of Day Transaction

Count (MILSTRAP DZM) and to Provide Transaction Clarification and Administrative Changes (Supply)

- ADC 198, Revise DS 846P to Provide Capability to Advise When No History is Available in Response to a Transaction History Request

1. This transaction is used to request, inquire about, and cancel a physical inventory, and to request transaction history. Use one occurrence

of this transaction set to transmit a single or multiple transactions.

a. Owners and managers use this transaction set to request, inquire about, and cancel a physical inventory by a distribution center or

storage activity. Owners and managers also use this transaction set to request transaction history. Distribution depots/storage activities use

this transaction set to cancel and/or reschedule a physical inventory request by an owner/manager. Distribution depots/storage activities

also use this transaction set to respond to a request for transaction history when no history is available and an inquiry about a request for a

physical inventory. Distribution depots/storage activities also use this transaction set to provide the owner/manager End of Day processing

transactions count information. This transaction encompasses the functionality of MILSTRAP Document Identifier Codes (DIC) DJA, DZJ,

DZK when rp 30-43 is 8-filled or 9-filled, and DZM. This transaction also accommodates the functionality of non-DLSS Navy DIC BZA and

BZC.

2. Use a single occurrence of this transaction set to exchange transactions between a single owner/manager and a single or multiple

distribution depots/storage activities, or between a single distribution depot/storage activity and a single or multiple owners/managers. For

use as an end of day transaction count, depot/storage activity sends a single occurrence of this transaction to a single owner/manager.

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

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

4. This DLMS Implementation Convention (IC) 846P 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 field 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 DLSS

transactions.

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

of the ANSI X12 standard, such data is not compatible with DLSS/DLMS conversion and may not be supported by the recipient's automated

processing system. Components must coordinate implementation of enhanced capability with DEDSO prior to use.

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

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

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

inappropriate rejection of the transaction.

5. This DLMS IC incorporates the Proposed DLMS Change (PDC) and Approved DLMS Change (ADC) listed. PDCs/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 134, Revision to DS 846P, Physical Inventory Request to Add Physical Inventory Cutoff Date (Supply)

- ADC 138, Revisions to DLMS Supplement (DS) 846P, Physical Inventory Request, to Capture Impact of Approved DLMS Change (ADC)

33, and Other Administrative Changes

- ADC 164, Revision to DLMS Supplement 846P, Physical Inventory Request, to Accommodate Functionality of End of Day Transaction

Count (MILSTRAP DZM) and to Provide Transaction Clarification and Administrative Changes (Supply)

- ADC 198, Revise DS 846P to Provide Capability to Advise When No History is Available in Response to a Transaction History Request
DLMS Implementation Convention (IC) 846P

Physical Inventory Request

ADC 45, 77, 134, 138, 164, 198, 204, 270, 295, 307, 320, 381, 381A, 393, 436, 1043C, 1224, 1224A, 1228,

1244, 1254, 1287, 1349, 1367, 1412 and 1454 DLM 4000.25

004010F846P4PA23 2 August 21, 2023

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

Process (Supply)

- ADC 270, Administrative Revision to DS 846P to Clarify Date Qualifiers in Transaction History Requests

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

and 888I (Supply/MILSTRAP) (Supply/MILSTRAP)

- ADC 320, Revises DS 846P to Add Transaction Creation Date; Intra-Navy Change to Migrate Navy BZA/BZC Data Requirements to 846P

End of Day Transaction Count Function (Supply)

- 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 393, Revise DLMS 846P, Response to Transaction History Request When No History Available, to Add a Second Iteration of Type

Physical Inventory/Transaction History Code

- 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

- Organizational Name and Other Non-Substantive (Administrative) Updates Completed on July 29, 2015.

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

- 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 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 1254, Remove Unit of Measure Code Validation from DLMS XML Schemas

- 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

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

January 22, 2019

- ADC 1349, Revision to DLMS 846P and 140A for Air Force Government Furnished Property – Accountability

- 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 1454, Expand Use of Shop Service Center Codes in Defense Logistics Management Standards Transactions

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

Process (Supply)

- ADC 270, Administrative Revision to DS 846P to Clarify Date Qualifiers in Transaction History Requests

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

and 888I (Supply/MILSTRAP) (Supply/MILSTRAP)

- ADC 320, Revises DS 846P to Add Transaction Creation Date; Intra-Navy Change to Migrate Navy BZA/BZC Data Requirements to 846P

End of Day Transaction Count Function (Supply)

- 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 393, Revise DLMS 846P, Response to Transaction History Request When No History Available, to Add a Second Iteration of Type

Physical Inventory/Transaction History Code

- 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

- Organizational Name and Other Non-Substantive (Administrative) Updates Completed on July 29, 2015.

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

- 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 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 1254, Remove Unit of Measure Code Validation from DLMS XML Schemas

- 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

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

January 22, 2019

- ADC 1349, Revision to DLMS 846P and 140A for Air Force Government Furnished Property – Accountability

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

10 ST Transaction Set Header M 1 Must use

20 BIA Beginning Segment for Inventory

Inquiry/Advice

M 1 Must use

* 40 CUR Currency O 1 Not Used

* 50 DTM Date/Time Reference O 10 Not Used

* 60 REF Reference Identification O 12 Not Used

* 70 PER Administrative Communications

Contact

O 3 Not Used

* 75 MEA Measurements O 20 Not Used

LOOP ID - N1 LOOP ID - N1 5

80 N1 Name O 1 Must use

* 90 N2 Additional Name Information O 2 Not Used

* 100 N3 Address Information O 2 Not Used

* 110 N4 Geographic Location O 1 Not Used

* 120 REF Reference Identification O 12 Not Used

* 130 PER Administrative Communications

Contact

O 3 Not Used

* LOOP ID - LM * LOOP ID - LM 10
DLMS Implementation Convention (IC) 846P

Physical Inventory Request

ADC 45, 77, 134, 138, 164, 198, 204, 270, 295, 307, 320, 381, 381A, 393, 436, 1043C, 1224, 1224A, 1228,

1244, 1254, 1287, 1349, 1367, 1412 and 1454 DLM 4000.25

Pos Id Segment Name Req Max Use Repeat Notes Usage

004010F846P4PA23 3 August 21, 2023

* 140 LM Code Source Information O 1 Not 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

10 LIN Item Identification M 1 Must use

* 30 PID Product/Item Description O 200 Not Used

* 40 MEA Measurements O 40 Not Used

* 50 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 Not Used

* 300 MEA Measurements O 40 Not Used

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

* LOOP ID - MAN * LOOP ID - MAN 100

* 312 MAN Marks and Numbers O 1 Not Used

* 314 MEA Measurements O 40 Not 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 Not Used

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

* 375 LM Code Source Information O 1 Not Used

376 LQ Industry Code M 100 Must use

* LOOP ID - LS * LOOP ID - LS 1

* 380 LS Loop Header O 1 Not Used
DLMS Implementation Convention (IC) 846P

Physical Inventory Request

ADC 45, 77, 134, 138, 164, 198, 204, 270, 295, 307, 320, 381, 381A, 393, 436, 1043C, 1224, 1224A, 1228,

1244, 1254, 1287, 1349, 1367, 1412 and 1454 DLM 4000.25

Pos Id Segment Name Req Max Use Repeat Notes Usage

004010F846P4PA23 4 August 21, 2023

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

* 390 REF Reference Identification O 1 N2/390 Not Used

* 400 DTM Date/Time Reference O >1 Not Used

* 410 N1 Name O 1 Not Used

* LOOP ID - LM * LOOP ID - LM 10

* 420 LM Code Source Information O 1 Not Used

430 LQ Industry Code M 100 Must use

* 440 LE Loop Trailer M 1 Not Used

LOOP ID - N1 LOOP ID - N1 200

450 N1 Name O 1 Must use

* 460 N2 Additional Name Information O 2 Not Used

* 470 N3 Address Information O 2 Not Used

* 480 N4 Geographic Location O 1 Not Used

* 490 REF Reference Identification O 12 Not Used

* 500 PER Administrative Communications

Contact

O 3 Not Used

Summary:

Pos Id Segment Name Req Max Use Repeat Notes Usage

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

20 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/10 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) 846P

Physical Inventory Request

ADC 45, 77, 134, 138, 164, 198, 204, 270, 295, 307, 320, 381, 381A, 393, 436, 1043C, 1224, 1224A, 1228,

1244, 1254, 1287, 1349, 1367, 1412 and 1454 DLM 4000.25

004010F846P4PA23 5 August 21, 2023

ST Transaction Set Header Pos: 10 Max: 1

Heading - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must use

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

Semantics: 

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

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

ST01 143 Transaction Set Identifier Code

Description: Code uniquely identifying a

Transaction Set

M ID 3/3 Must use 1

CodeList Summary (Total Codes: 298, Included: 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) 846P

Physical Inventory Request

ADC 45, 77, 134, 138, 164, 198, 204, 270, 295, 307, 320, 381, 381A, 393, 436, 1043C, 1224, 1224A, 1228,

1244, 1254, 1287, 1349, 1367, 1412 and 1454 DLM 4000.25

004010F846P4PA23 6 August 21, 2023

BIA Beginning Segment for Inventory

Inquiry/Advice

Pos: 20 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.

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

CodeList Summary (Total Codes: 65, Included: 3)

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

CodeList Summary (Total Codes: 522, Included: 5)

Code Name

AD Agent/Distributor Inventory Report

DLMS Note:

Use to identify a Response to a Transaction History Request (No History Available). From distribution

depot/storage activity to owner/manager. (MILSTRAP DIC DZK functionality when record position 30-43

is 8-filled or 9-filled.) Use with 2/LQ01/270/FC Type of Physical Inventory/Transaction History Code 8 or

9. NOTE: When history is available, there is no direct map of MILSTRAP DIC DZK to DLMS. Instead,

all transactions that were subject to historical submission under DZK, were given a beginning segment

action code ‘W1” for historical submissions. DLMS transactions containing Action Code W1 for

historical submission are: 527R, 867I, 940R, 945A, 947I.)

Use to identify a Response to a Transaction History Request (No History Available). From distribution

depot/storage activity to owner/manager. (MILSTRAP DIC DZK functionality when record position 30-43

is 8-filled or 9-filled.) Use with 2/LQ01/270/FC Type of Physical Inventory/Transaction History Code 8 or

9. NOTE: When history is available, there is no direct map of MILSTRAP DIC DZK to DLMS. Instead,

all transactions that were subject to historical submission under DZK, were given a beginning segment

action code ‘W1” for historical submissions. DLMS transactions containing Action Code W1 for

historical submission are: 527R, 867I, 940R, 945A, 947I.)

B1 Batch Report

DLMS Note:

1. Use to identify End of Day Transaction Count. Use to provide end of day accountable transaction

count information. From distribution depot/storage activity to owner/manager to advise owner/manager

of the number of balance affecting transactions that were forwarded during the daily course of business.

 (MILSTRAP DIC DZM functionality).

2. Sent by distribution depot/storage activity to owner/manager to advise owner/manager of the 
DLMS Implementation Convention (IC) 846P

Physical Inventory Request

ADC 45, 77, 134, 138, 164, 198, 204, 270, 295, 307, 320, 381, 381A, 393, 436, 1043C, 1224, 1224A, 1228,

1244, 1254, 1287, 1349, 1367, 1412 and 1454 DLM 4000.25

Code Name

004010F846P4PA23 7 August 21, 2023

number of accountable (balance affecting) transactions that were forwarded during the daily course of

business. Only the following qualify as accountable transactions for this purpose: Receipts (DLMS IC

527R with 1/BR02 code D4); Issues (DLMS IC 867I); Inventory Adjustment-Increases (DLMS IC 947I

with 2/W1916 code AJ); Inventory Adjustment-Decreases (DLMS IC 947I with 2/W1916 code AD);

Inventory Adjustments-Dual (DLMS IC 947I with 2/W1916 code DU).

DD Distributor Inventory Report

DLMS Note:

Use to identify a Response to Physical Inventory Request Transaction (does not include asset

balances). From distribution depot/storage activity to owner/manager. (MILSTRAP DIC DJA

functionality when used as a response with Management Code R (no record of stock number or no

record of ownership), S (physical inventory in workload bank or in process), or Y (response to follow-up

when inventory already complete).

TC Physical Inventory Request

DLMS Note:

Use to identify a Physical Inventory Request Transaction. From owner/manager to initiate, follow up on,

or cancel a physical inventory. From distribution depot/storage activity to initiate or cancel a physical

inventory. (MILSTRAP DIC DJA functionality)

TF Transaction History Request

DLMS Note:

Use to identify a Transaction History Request Transaction. From owner/manager to distribution

depot/storage activity. (MILSTRAP DIC DZJ functionality).

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 date is the date of the

transaction set preparation and

corresponds to the Universal Time

Coordinate (UTC).

2. Authorized DLMS enhancement; see

introductory DLMS note 4g. 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 4g. on IC cover

page.

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

Physical Inventory Request

ADC 45, 77, 134, 138, 164, 198, 204, 270, 295, 307, 320, 381, 381A, 393, 436, 1043C, 1224, 1224A, 1228,

1244, 1254, 1287, 1349, 1367, 1412 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F846P4PA23 8 August 21, 2023

BIA06 306 Action Code

Description: Code indicating type of action

DLMS Note: The following code is

authorized.

O ID 1/2 Used 0

CodeList Summary (Total Codes: 296, Included: 1)

Code Name

ND No Change

DLMS Note:

1. Authorized for intra-Navy use only for a Navy requirement; see introductory DLMS note 4e. Use in

conjunction with BIA02 code ‘B1’. Navy reporting activities use with end of day processing to advise

Navy ICPs that no balance affecting transactions were submitted that day. (An ANSI data maintenance

request has been prepared to establish a new data element 1270 code qualifier assignment for 'No

Balance Affecting Transactions’. (Navy DIC BZA functionality. Refer to ADC 320)

2. Use other than as noted above is a DLMS enhancement. See introductory DLMS note 4a.

1. Authorized for intra-Navy use only for a Navy requirement; see introductory DLMS note 4e. Use in

conjunction with BIA02 code ‘B1’. Navy reporting activities use with end of day processing to advise

Navy ICPs that no balance affecting transactions were submitted that day. (An ANSI data maintenance

request has been prepared to establish a new data element 1270 code qualifier assignment for 'No

Balance Affecting Transactions’. (Navy DIC BZA functionality. Refer to ADC 320)

2. Use other than as noted above is a DLMS enhancement. See introductory DLMS note 4a.
DLMS Implementation Convention (IC) 846P

Physical Inventory Request

ADC 45, 77, 134, 138, 164, 198, 204, 270, 295, 307, 320, 381, 381A, 393, 436, 1043C, 1224, 1224A, 1228,

1244, 1254, 1287, 1349, 1367, 1412 and 1454 DLM 4000.25

004010F846P4PA23 9 August 21, 2023

N1 Name Pos: 80 Max: 1

Heading - Optional

Loop: N1 Elements: 4

User Option (Usage): Must use

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

Syntax Rules: 

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

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

Comments: 

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

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

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

DLMS Note:

Must use one 1/N1/080 loop to identify the organization originating the transaction set.

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 SB

or Z4; or for intra-Navy use, Navy may use

code FA as noted.

2. The following codes are authorized.

M ID 2/3 Must use 1

CodeList Summary (Total Codes: 1312, Included: 5)

Code Name

FA Facility

DLMS Note:

1. Authorized for intra-Navy use. Commercial Asset Visibility-Organic Repair Module (CAV-ORM) uses

with 1/BIA01/20 Report Type Code B1, End of Day Transaction Count transactions, to identify an

organic repair facility (e.g., shipyard or Fleet Readiness Center (FRC)). Authorized DLMS migration

enhancement for intra-Navy use; see introductory DLMS note 4g. Refer to ADC 320.

2. Use other than as noted above is a DLMS enhancement. See introductory DLMS note 4a.

OW Owner of Property or Unit

DLMS Note:

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

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

DoDAAC does not have an assigned RIC, use the generic Air Force GFP APSR RIC with 1/N106=FR

and use a second iteration of the N1 loop (repeating Code OW without 1/N106=FR) to provide the

program manager DoDAAC. Refer to ADC 1224 and ADC 1349.

SB Storage Area

DLMS Note:

1. Use to indicate the depot or storage activity.

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.
DLMS Implementation Convention (IC) 846P

Physical Inventory Request

ADC 45, 77, 134, 138, 164, 198, 204, 270, 295, 307, 320, 381, 381A, 393, 436, 1043C, 1224, 1224A, 1228,

1244, 1254, 1287, 1349, 1367, 1412 and 1454 DLM 4000.25

Code Name

004010F846P4PA23 10 August 21, 2023

3. Refer to ADCs 284A, 381, and 1454 for known applications.

Z4 Owning Inventory Control Point

N103 66 Identification Code Qualifier

Description: Code designating the

system/method of code structure used for

Identification Code (67)

X ID 1/2 Must use 1

CodeList Summary (Total Codes: 215, Included: 3)

Code Name

10 Department of Defense Activity Address Code (DODAAC)

DLMS Note:

DLMS enhancement; see introductory DLMS note 4a.

92 Assigned by Buyer or Buyer's Agent

DLMS Note:

Use with N101 Code XN to identify the user assigned Shop Service Center/Shop Store Identifier. Refer

to ADCs 284A, 381 and 1454.

M4 Department of Defense Routing Identifier Code (RIC)

N104 67 Identification Code

Description: Code identifying a party or

other code

X AN 2/80 Must use 1

N106 98 Entity Identifier Code

Description: Code identifying an

organizational entity, a physical location,

property or an individual

O ID 2/3 Used 1

CodeList Summary (Total Codes: 1312, Included: 1)

Code Name

FR Message From

DLMS Note:

Must use one iteration with the appropriate 1/N101/080 code to indicate the organization cited in N104

originating the transaction set.
DLMS Implementation Convention (IC) 846P

Physical Inventory Request

ADC 45, 77, 134, 138, 164, 198, 204, 270, 295, 307, 320, 381, 381A, 393, 436, 1043C, 1224, 1224A, 1228,

1244, 1254, 1287, 1349, 1367, 1412 and 1454 DLM 4000.25

004010F846P4PA23 11 August 21, 2023

LIN Item Identification Pos: 10 Max: 1

Detail - Mandatory

Loop: LIN Elements: 4

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

Comments: 

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

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

ISBN No., Model No., or SKU.

DLMS Note:

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

2. For End of Day Transaction count (1/BIA02/20 code B1), repeat the LIN loop as needed to provide the transaction number and

accountable transaction count information. Use one iteration to identify the number of different transaction “types” being reported. Use

additional iterations as needed to provide transaction counts for the specific transaction types.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

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/20 codes AD,

DD, TC, and TF, use only one of codes A2,

A3, A4, FB, FS, MG, SW, YP, ZR or ZZ to

identify the item 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.

DLMS Note: 1. For 1/BIA02/20 codes AD,

DD, TC, and TF, use only one of codes A2,

A3, A4, FB, FS, MG, SW, YP, ZR or ZZ to

identify the item 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/20 code B1, only use ZZ.

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

Physical Inventory Request

ADC 45, 77, 134, 138, 164, 198, 204, 270, 295, 307, 320, 381, 381A, 393, 436, 1043C, 1224, 1224A, 1228,

1244, 1254, 1287, 1349, 1367, 1412 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F846P4PA23 12 August 21, 2023

3. The following codes are authorized.

CodeList Summary (Total Codes: 477, Included: 13)

Code Name

A2 Department of Defense Identification Code (DoDIC)

DLMS Note:

1. Use to identify ammunition items.

2. Authorized migration enhancement for intra-Navy use only; see introductory DLMS note 4g. Refer to

ADC 320.

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

cross-reference.

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

LSN will also be included for cross-reference.

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

381/Approved Addendum 381A.

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

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

cross-reference.

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

LSN will also be included for cross-reference.

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

381/Approved Addendum 381A.
DLMS Implementation Convention (IC) 846P

Physical Inventory Request

ADC 45, 77, 134, 138, 164, 198, 204, 270, 295, 307, 320, 381, 381A, 393, 436, 1043C, 1224, 1224A, 1228,

1244, 1254, 1287, 1349, 1367, 1412 and 1454 DLM 4000.25

Code Name

004010F846P4PA23 13 August 21, 2023

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 Material 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. Dual use:

For 1/BIA02/20 codes AD, DD, TC, and TF, 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 1/BIA02/20 code B1 end of day accountable transaction count transactions, must use to comply

with ANSI syntax requirements. Indicate ZZ in LIN03.

1. Dual use:

For 1/BIA02/20 codes AD, DD, TC, and TF, 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 1/BIA02/20 code B1 end of day accountable transaction count transactions, 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

CodeList Summary (Total Codes: 477, Included: 3)

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.

ZB Commercial and Government Entity (CAGE) Code

DLMS Note:

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) 846P

Physical Inventory Request

ADC 45, 77, 134, 138, 164, 198, 204, 270, 295, 307, 320, 381, 381A, 393, 436, 1043C, 1224, 1224A, 1228,

1244, 1254, 1287, 1349, 1367, 1412 and 1454 DLM 4000.25

004010F846P4PA23 14 August 21, 2023

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. R020305 - At least one of DTM02, DTM03 or DTM05 is required.

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

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

DLMS Note:

1. Use to convey dates associated with the transaction.

2. Do not use with End of Day Accountable Transaction Count transactions (1/BIA02/20 code B1).

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

CodeList Summary (Total Codes: 1112, Included: 5)

Code Name

090 Report Start

DLMS Note:

Use in transaction history requests to identify the transaction history reporting start date. (Report start

date equates to MILSTRAP DIC DZJ rp 25-28 transaction history start date.) 

091 Report End

DLMS Note:

Use in transaction history requests to identify the transaction history reporting end date. (Report end

date is a date equivalent for MILSTRAP DIC DZJ rp 29-31 which is the total number of prior days

transaction history required. Accordingly, the report end date will precede the report start date.)

097 Transaction Creation

DLMS Note:

Use to identify the date the transaction was prepared.

197 End

DLMS Note:

Use to identify the Physical Inventory Cutoff Date (PICD).

501 Expected Reply

DLMS Note:

1. For Air Force GFP accountability, use to identify the due date established by the Air Force program

manager for the CICP response to the requested physical inventory. Use in conjunction with document

number assigned to this specific request (REF01 Code TN). Refer to ADC 1224.

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

DTM02 373 Date

Description: Date expressed as

CCYYMMDD

X DT 8/8 Must use 1

DTM03 337 Time

Description: Time expressed in 24-hour

clock time as follows: HHMM, or HHMMSS,

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

Physical Inventory Request

ADC 45, 77, 134, 138, 164, 198, 204, 270, 295, 307, 320, 381, 381A, 393, 436, 1043C, 1224, 1224A, 1228,

1244, 1254, 1287, 1349, 1367, 1412 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F846P4PA23 15 August 21, 2023

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

(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 4.g.
DLMS Implementation Convention (IC) 846P

Physical Inventory Request

ADC 45, 77, 134, 138, 164, 198, 204, 270, 295, 307, 320, 381, 381A, 393, 436, 1043C, 1224, 1224A, 1228,

1244, 1254, 1287, 1349, 1367, 1412 and 1454 DLM 4000.25

004010F846P4PA23 16 August 21, 2023

REF Reference Identification Pos: 140 Max: >1

Detail - Optional

Loop: LIN Elements: 2

User Option (Usage): Used

Purpose: To specify identifying information

Syntax Rules: 

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

Semantics: 

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

DLMS Note:

1. Use to identify the transaction number.

2. For End of Day Accountable Transaction Counts (1/BIA02/20 code B1) use to cite the accountable transaction count information (except

do not use to cite count information with intra-Navy BIA06 Action Code ‘ND’ which Navy uses to indicate no accountable transactions were

submitted that day).

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

CodeList Summary (Total Codes: 1503, Included: 6)

Code Name

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.

8X Transaction Category or Type

DLMS Note:

Use to identify the specific transaction types for which transaction counts are being provided in

2/QTY/320 (i.e., receipt, issue, inventory adjustment increase, inventory adjustment decrease,

inventory adjustment dual and release confirmations). 

For Receipts (DLMS IC 527R with 1/BR02 Code D4); Issues (DLMS IC 867I); Inventory

Adjustment-Increases (DLMS IC 947I with 2/W1916 Code AJ); Inventory Adjustment-Decreases (DLMS

IC 947I with 2/W1916 Code AD); Inventory Adjustments-Dual (DLMS IC 947I with 2/W1916 Code DU)

Cite the appropriate code in REF02 as follows:

For Receipts, cite 527R in REF02.

For Issues, cite 867I in REF02.

For Inventory Adjustment Increases, cite 947IAJ in REF02.

For Inventory Adjustment Decreases, cite 947IAD in REF02.

Use to identify the specific transaction types for which transaction counts are being provided in

2/QTY/320 (i.e., receipt, issue, inventory adjustment increase, inventory adjustment decrease,

inventory adjustment dual and release confirmations). 

For Receipts (DLMS IC 527R with 1/BR02 Code D4); Issues (DLMS IC 867I); Inventory

Adjustment-Increases (DLMS IC 947I with 2/W1916 Code AJ); Inventory Adjustment-Decreases (DLMS

IC 947I with 2/W1916 Code AD); Inventory Adjustments-Dual (DLMS IC 947I with 2/W1916 Code DU)

Cite the appropriate code in REF02 as follows:

For Receipts, cite 527R in REF02.

For Issues, cite 867I in REF02.

For Inventory Adjustment Increases, cite 947IAJ in REF02.

For Inventory Adjustment Decreases, cite 947IAD in REF02.
DLMS Implementation Convention (IC) 846P

Physical Inventory Request

ADC 45, 77, 134, 138, 164, 198, 204, 270, 295, 307, 320, 381, 381A, 393, 436, 1043C, 1224, 1224A, 1228,

1244, 1254, 1287, 1349, 1367, 1412 and 1454 DLM 4000.25

Code Name

004010F846P4PA23 17 August 21, 2023

For Inventory Adjustments Dual, cite 947IDU in REF02.

For intra-Air Force use, USAF CICP also provides transaction count for non-accountable transactions: 

For Materiel Release Advice (DLMS 945A with 1/W0611 code NJ or NM); For Receipt Acknowledge

(DLMS 527R with BR02 Code TH or CJ.

Cite the appropriate code in REF02 as follows: 

For Materiel Release Advice, cite 945A MRC/DRC in REF02. Refer to ADC 1228.

For Receipt Acknowledgement, cite 527R MRA/TRA in REF02. Refer to ADC 1228.

For intra-Navy use, Navy also provides transaction counts for non-accountable Asset Status Report

transactions (DLMS IC 846I with BIA02 code TJ), cite 846I in REF02. Refer to ADC 320.

For Inventory Adjustments Dual, cite 947IDU in REF02.

For intra-Air Force use, USAF CICP also provides transaction count for non-accountable transactions: 

For Materiel Release Advice (DLMS 945A with 1/W0611 code NJ or NM); For Receipt Acknowledge

(DLMS 527R with BR02 Code TH or CJ.

Cite the appropriate code in REF02 as follows: 

For Materiel Release Advice, cite 945A MRC/DRC in REF02. Refer to ADC 1228.

For Receipt Acknowledgement, cite 527R MRA/TRA in REF02. Refer to ADC 1228.

For intra-Navy use, Navy also provides transaction counts for non-accountable Asset Status Report

transactions (DLMS IC 846I with BIA02 code TJ), cite 846I in REF02. Refer to ADC 320.

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.

FI File Identifier

DLMS Note:

Use with 1/BIA02/20 code B1. Use to indicate that the number of different types of accountable

transactions is being reported in 2/QTY01-02/320. Enter “1” in REF02 for this purpose.

L1 Letters or Notes

DLMS Note:

For Intra-Navy use only, Navy uses to identify that End of Day Transaction Count transaction was

generated by applications other than CAV II. Navy cites ‘C’ in REF02 to indicate non CAV II

transactions. Navy uses with 1/BIA02/20 Code B1. Refer to ADC 320.

TN Transaction Reference Number

DLMS Note:

1. Use to identify the document number assigned by the materiel owner/manager as part of an physical

inventory request. The storage activity must perpetuate the document number in the response when

provided. Required for capital equipment candidates and UIT programs. Authorized DLMS

enhancement for all other commodities. Refer to ADC 1244.

2. For Air Force GFP accountability, use to identify the document number assigned by the Air Force

program manager in the accountable property system of record (APSR). The CICP must perpetuate the

document number to the response. Refer to ADC 1224. 

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

1. Use to identify the document number assigned by the materiel owner/manager as part of an physical

inventory request. The storage activity must perpetuate the document number in the response when

provided. Required for capital equipment candidates and UIT programs. Authorized DLMS

enhancement for all other commodities. Refer to ADC 1244.

2. For Air Force GFP accountability, use to identify the document number assigned by the Air Force

program manager in the accountable property system of record (APSR). The CICP must perpetuate the

document number to the response. Refer to ADC 1224. 

3. DLMS enhancement; 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 Must use 1
DLMS Implementation Convention (IC) 846P

Physical Inventory Request

ADC 45, 77, 134, 138, 164, 198, 204, 270, 295, 307, 320, 381, 381A, 393, 436, 1043C, 1224, 1224A, 1228,

1244, 1254, 1287, 1349, 1367, 1412 and 1454 DLM 4000.25

004010F846P4PA23 18 August 21, 2023

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.

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

CodeList Summary (Total Codes: 176, Included: 1)

Code Name

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

Physical Inventory Request

ADC 45, 77, 134, 138, 164, 198, 204, 270, 295, 307, 320, 381, 381A, 393, 436, 1043C, 1224, 1224A, 1228,

1244, 1254, 1287, 1349, 1367, 1412 and 1454 DLM 4000.25

004010F846P4PA23 19 August 21, 2023

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: 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: 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 Must use 1

CodeList Summary (Total Codes: 558, Included: 17)

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.

78 Project Code

DLMS Note:

1. Enter the project code in LQ02 if stocks are segregated and maintained by project codes.

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

83 Supply Condition Code

84 Management Code

DLMS Note:

Use in physical inventory request, physical inventory report/response, to provide supplemental

management information.

87 Subsistence Type of Pack Code

DLMS Note:

Use in physical inventory request and physical inventory response transactions to further identify

subsistence items.

99 Purpose Code

DLMS Note:

1. Enter the purpose code in LQ02 if stocks are segregated and maintained by purpose codes.

A1 Ownership Code

DLMS Note:

1. Enter the ownership code in LQ02 if stocks are segregated and maintained by ownership codes.

A9 Supplemental Data
DLMS Implementation Convention (IC) 846P

Physical Inventory Request

ADC 45, 77, 134, 138, 164, 198, 204, 270, 295, 307, 320, 381, 381A, 393, 436, 1043C, 1224, 1224A, 1228,

1244, 1254, 1287, 1349, 1367, 1412 and 1454 DLM 4000.25

Code Name

004010F846P4PA23 20 August 21, 2023

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.

AK Distribution Code

DLMS Note:

1. Enter the distribution code in LQ02 if stocks are segregated and maintained by distribution codes.

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

DF Media and Status Code

DLMS Note:

The DLMS provides the capability to carry additional status recipients beyond those identified by the

DLSS. The Media and Status Code and the Distribution Code will be retained in the DLMS to facilitate

transaction conversion in a mixed DLSS/DLMS environment. Additional status recipients identified here

cannot be passed to DLSS users.

FC Type Physical Inventory or Transaction History Code

DLMS Note:

1. For Physical Inventory Request Transaction, Response to Physical Inventory Request Transaction,

and Transaction History Request (1/BIA02/20 Report Type Codes TC, DD, and TF respectively), cite

appropriate code.

 2. For Response to Transaction History Request (No History Available) (BIA02 Report Type Code AD),

code value 8 or 9 is required; in addition, a second iteration of qualifier FC is used to perpetuate the

code which appeared on the Transaction History Request or cite code W or Y (DLA only) for automatic

submission of transaction history. Refer to ADC 198 and ADC 393. 

1. For Physical Inventory Request Transaction, Response to Physical Inventory Request Transaction,

and Transaction History Request (1/BIA02/20 Report Type Codes TC, DD, and TF respectively), cite

appropriate code.

 2. For Response to Transaction History Request (No History Available) (BIA02 Report Type Code AD),

code value 8 or 9 is required; in addition, a second iteration of qualifier FC is used to perpetuate the

code which appeared on the Transaction History Request or cite code W or Y (DLA only) for automatic

submission of transaction history. Refer to ADC 198 and ADC 393. 

GQ Group Qualifier Code

DLMS Note:

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

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

Force-unique data element, meaningful to the Air Force only. Non-Air Force Components perpetuate

without action.

A data maintenance action was approved in version 5010. The approved code/name is "MAC – Material

Management Aggregation Code". The code source is identified as the Air Force Manual (AFMAN)

23-110, Volumes 1 and 2.

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

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

Force-unique data element, meaningful to the Air Force only. Non-Air Force Components perpetuate

without action.

A data maintenance action was approved in version 5010. The approved code/name is "MAC – Material

Management Aggregation Code". The code source is identified as the Air Force Manual (AFMAN)

23-110, Volumes 1 and 2.

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.
DLMS Implementation Convention (IC) 846P

Physical Inventory Request

ADC 45, 77, 134, 138, 164, 198, 204, 270, 295, 307, 320, 381, 381A, 393, 436, 1043C, 1224, 1224A, 1228,

1244, 1254, 1287, 1349, 1367, 1412 and 1454 DLM 4000.25

004010F846P4PA23 21 August 21, 2023

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) 846P

Physical Inventory Request

ADC 45, 77, 134, 138, 164, 198, 204, 270, 295, 307, 320, 381, 381A, 393, 436, 1043C, 1224, 1224A, 1228,

1244, 1254, 1287, 1349, 1367, 1412 and 1454 DLM 4000.25

004010F846P4PA23 22 August 21, 2023

QTY Quantity Pos: 320 Max: 1

Detail - Optional

Loop: QTY Elements: 3

User Option (Usage): Used

Purpose: To specify quantity information

Syntax Rules: 

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

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

Semantics: 

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

QTY01 673 Quantity Qualifier

Description: Code specifying the type of

quantity

M ID 2/2 Must use 1

CodeList Summary (Total Codes: 832, Included: 4)

Code Name

02 Cumulative Quantity

DLMS Note:

For intra-Navy use only, Navy Commercial Asset Visibility (CAV) uses with 1/BIA02/20 code ‘B1-End of

Day Transaction Count’, to identify the summary quantity for the transactions being reported. This

equates to Navy DIC BZC, rp 7-11. Not used with intra-Navy BIA06 Action Code ‘ND’. Refer to ADC

320.

46 Total transactions

DLMS Note:

Use with BIA02 code B1 End of Day Transaction Count and 2/REF01 code FI to indicate the total

number of balance affecting transaction types being reported in this transaction. For the purpose of this

transaction there are 5 possible transaction types for which end of day counts can be reported (receipts,

issues, inventory adjustment increases, inventory adjustment decreases, and inventory adjustment

dual.). Not used with intra-Navy BIA06 Action Code ‘ND’.

TT Total Production Volume

DLMS Note:

Use with BIA02 code B1 End of Day Transaction Count to indicate the daily volume of balance affecting

transactions applicable to the transaction category/type identified in 2/REF01/140 code 8X (e.g. if 36

receipt transactions are being reported, REF01 = 8X; REF02 = 527R; QTY01 = TT; QTY02 = 36.) Not

used with intra-Navy BIA06 Action Code ‘ND’.

UU Used

DLMS Note:

For BIA02 codes AD, DD, TC, DF, and BIA06 Action Code ND, use to comply with X12 syntax

requirements. Cite “1” in QTY02. Do not use with BIA02 code B1 (except when B1 is used in

conjunction with intra-Navy BIA06 Action Code ‘ND’).

QTY02 380 Quantity

Description: Numeric value of quantity

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

QTY03-01 355 Unit or Basis for Measurement Code

Description: Code specifying the units in

which a value is being expressed, or

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

Physical Inventory Request

ADC 45, 77, 134, 138, 164, 198, 204, 270, 295, 307, 320, 381, 381A, 393, 436, 1043C, 1224, 1224A, 1228,

1244, 1254, 1287, 1349, 1367, 1412 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F846P4PA23 23 August 21, 2023

manner in which a measurement has been

taken

DLMS Note: 1. Use any code other than

ZZ.

2. DLMS users see the DLMS Unit of Issue

and Purchase Unit Conversion Table for

available codes.
DLMS Implementation Convention (IC) 846P

Physical Inventory Request

ADC 45, 77, 134, 138, 164, 198, 204, 270, 295, 307, 320, 381, 381A, 393, 436, 1043C, 1224, 1224A, 1228,

1244, 1254, 1287, 1349, 1367, 1412 and 1454 DLM 4000.25

004010F846P4PA23 24 August 21, 2023

N1 Name Pos: 450 Max: 1

Detail - Optional

Loop: N1 Elements: 4

User Option (Usage): Must use

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

Syntax Rules: 

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

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

Comments: 

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

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

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

DLMS Note:

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 one of codes SB or Z4.

2. The following codes are authorized.

M ID 2/3 Must use 1

CodeList Summary (Total Codes: 1312, Included: 5)

Code Name

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. For Air Force GFP accountability, use to identify the Air Force program manager in the accountable

property system of record (APSR). Refer to ADC 1224

2. For transactions directed to the 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. 

3. For transactions sent from the APSR using the generic Air Force GFP APSR RIC 1/N101/80 Code

OW), use to identify the program manager DoDAAC.

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

property system of record (APSR). Refer to ADC 1224

2. For transactions directed to the 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. 

3. For transactions sent from the APSR using the generic Air Force GFP APSR RIC 1/N101/80 Code

OW), use to identify the program manager DoDAAC.

SB Storage Area

DLMS Note:

1. Use to indicate the depot or storage activity.

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.
DLMS Implementation Convention (IC) 846P

Physical Inventory Request

ADC 45, 77, 134, 138, 164, 198, 204, 270, 295, 307, 320, 381, 381A, 393, 436, 1043C, 1224, 1224A, 1228,

1244, 1254, 1287, 1349, 1367, 1412 and 1454 DLM 4000.25

Code Name

004010F846P4PA23 25 August 21, 2023

2. Use in conjunction with N103 Identification Code Qualifier 92.

3. Refer to ADCs 284A, 381, and 1454 for known applications.

Z4 Owning Inventory Control Point

N103 66 Identification Code Qualifier

Description: Code designating the

system/method of code structure used for

Identification Code (67)

X ID 1/2 Must use 1

CodeList Summary (Total Codes: 215, Included: 3)

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 Must use 1

N106 98 Entity Identifier Code

Description: Code identifying an

organizational entity, a physical location,

property or an individual

O ID 2/3 Used 1

CodeList Summary (Total Codes: 1312, Included: 1)

Code Name

TO Message To

DLMS Note:

Must use with the appropriate 2/N101/450 code to indicate the organization cited in N104 is receiving

the transaction.
DLMS Implementation Convention (IC) 846P

Physical Inventory Request

ADC 45, 77, 134, 138, 164, 198, 204, 270, 295, 307, 320, 381, 381A, 393, 436, 1043C, 1224, 1224A, 1228,

1244, 1254, 1287, 1349, 1367, 1412 and 1454 DLM 4000.25

004010F846P4PA23 26 August 21, 2023

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