DLMS Implementation Convention (IC) 846S Logistics Reassignment Storage

Information Order/Reply

ADC 66, 77, 151, 260, 436, 1043C, 1232, 1254, 1367 and 1412 

DLM 4000.25

004010F846S2SA09 1 March 8, 2022

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. Organizations use this transaction set to notify the distribution depot that ownership of stored wholesale assets has changed, to request

asset information, and to report asset information. Use one occurrence of this transaction set to transmit a single or multiple transactions. 

b. Losing Item Mangers (LIMs) use this transaction set to notify the distribution depot that ownership of stored wholesale assets has

transferred to the Gaining Item Manger (GIM) and to request asset information. Distribution depots use this transaction set to report asset

information to the LIM. This transaction encompasses the functionality of MILSTRAP Document Identifier Codes (DIC) DZC and DZD.

2. Use a single occurrence of this transaction set to exchange transactions between a single LIM and a single or multiple distribution depots,

or between a single distribution depot and a single or multiple LIMs.

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

identification to Defense Logistics Management Standards and incorporation into the DLMS.

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

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

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

5. This DLMS Implementation Convention (IC) 846S 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. Repetition of data using multiple iteration or loops is not compatible with existing DLSS capability. Although supported by 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.

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

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.

6. 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 66, Revision of DS 846S, Logistics Reassignment Storage Transfer Order/Reply

- ADC 77, Air Force Unique Management Coding for Material Management Aggregation Code.

- ADC 151, Administrative Revisions to DLMS Supplement 846L, Logistics Asset Support and 846S, Logistics Reassignment Storage

Transfer/Order/Reply (Supply)

- ADC 260, Revise DLMS and MILSTRAP to Support Intra-Army Logistics Reassignment (LR) Requirement, DLMS Supplement (DS) 846D

and DS 846S LR Transactions (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 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 August 07, 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 January 06, 2017

1a. Organizations use this transaction set to notify the distribution depot that ownership of stored wholesale assets has changed, to request

asset information, and to report asset information. Use one occurrence of this transaction set to transmit a single or multiple transactions. 

b. Losing Item Mangers (LIMs) use this transaction set to notify the distribution depot that ownership of stored wholesale assets has

transferred to the Gaining Item Manger (GIM) and to request asset information. Distribution depots use this transaction set to report asset

information to the LIM. This transaction encompasses the functionality of MILSTRAP Document Identifier Codes (DIC) DZC and DZD.

2. Use a single occurrence of this transaction set to exchange transactions between a single LIM and a single or multiple distribution depots,

or between a single distribution depot and a single or multiple LIMs.

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

identification to Defense Logistics Management Standards and incorporation into the DLMS.

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

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

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

5. This DLMS Implementation Convention (IC) 846S 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. Repetition of data using multiple iteration or loops is not compatible with existing DLSS capability. Although supported by 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.

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

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.

6. 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 66, Revision of DS 846S, Logistics Reassignment Storage Transfer Order/Reply

- ADC 77, Air Force Unique Management Coding for Material Management Aggregation Code.

- ADC 151, Administrative Revisions to DLMS Supplement 846L, Logistics Asset Support and 846S, Logistics Reassignment Storage

Transfer/Order/Reply (Supply)

- ADC 260, Revise DLMS and MILSTRAP to Support Intra-Army Logistics Reassignment (LR) Requirement, DLMS Supplement (DS) 846D

and DS 846S LR Transactions (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 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 August 07, 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 January 06, 2017
DLMS Implementation Convention (IC) 846S Logistics Reassignment Storage

Information Order/Reply

ADC 66, 77, 151, 260, 436, 1043C, 1232, 1254, 1367 and 1412 

DLM 4000.25

004010F846S2SA09 2 March 8, 2022

- ADC 1232, Revision to DLMS 846D and 846S Logistics Reassignment Transactions to Support Government Furnished Property (GFP)

Accountability during Logistics Reassignment between Air Force Contractor Inventory Control Points (CICP) and Air Force or DLA ICPs

- ADC 1254, Remove Unit of Measure Code Validation from DLMS XML Schemas

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

August 09, 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 8, 2022

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

Indicator to Wide Area Workflow

- ADC 1232, Revision to DLMS 846D and 846S Logistics Reassignment Transactions to Support Government Furnished Property (GFP)

Accountability during Logistics Reassignment between Air Force Contractor Inventory Control Points (CICP) and Air Force or DLA ICPs

- ADC 1254, Remove Unit of Measure Code Validation from DLMS XML Schemas

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

August 09, 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 8, 2022

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

Indicator to Wide Area Workflow

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

* 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
DLMS Implementation Convention (IC) 846S Logistics Reassignment Storage

Information Order/Reply

ADC 66, 77, 151, 260, 436, 1043C, 1232, 1254, 1367 and 1412 

DLM 4000.25

Pos Id Segment Name Req Max Use Repeat Notes Usage

004010F846S2SA09 3 March 8, 2022

* LOOP ID - LM * LOOP ID - LM 10

* 260 LM Code Source Information O 1 Not Used

* 270 LQ Industry Code M 100 Not Used

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

376 LQ Industry Code M 100 Must use

* LOOP ID - LS * LOOP ID - LS 1

* 380 LS Loop Header O 1 Not Used

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

* 440 LE Loop Trailer M 1 Not Used

LOOP ID - N1 LOOP ID - N1 200

450 N1 Name O 1 Used

* 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

* 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 
DLMS Implementation Convention (IC) 846S Logistics Reassignment Storage

Information Order/Reply

ADC 66, 77, 151, 260, 436, 1043C, 1232, 1254, 1367 and 1412 

DLM 4000.25

004010F846S2SA09 4 March 8, 2022

of the quantities (QTY02) of each QTY segment.
DLMS Implementation Convention (IC) 846S Logistics Reassignment Storage

Information Order/Reply

ADC 66, 77, 151, 260, 436, 1043C, 1232, 1254, 1367 and 1412 

DLM 4000.25

004010F846S2SA09 5 March 8, 2022

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

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) 846S Logistics Reassignment Storage

Information Order/Reply

ADC 66, 77, 151, 260, 436, 1043C, 1232, 1254, 1367 and 1412 

DLM 4000.25

004010F846S2SA09 6 March 8, 2022

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.

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

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.

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

Code Name

PK Storage Information Inquiry

DLMS Note:

Use to identify a Logistics Reassignment (LR) Storage Information Order. (MILSTRAP DIC DZC

functionality.)

TQ Storage Information Advice

DLMS Note:

Use to identify an LR Storage Information Reply. (MILSTRAP DIC DZD 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

transaction set preparation and

M DT 8/8 Must use 1
DLMS Implementation Convention (IC) 846S Logistics Reassignment Storage

Information Order/Reply

ADC 66, 77, 151, 260, 436, 1043C, 1232, 1254, 1367 and 1412 

DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F846S2SA09 7 March 8, 2022

corresponds to the Universal Time

Coordinate (UTC).

2. Authorized DLMS enhancement; see

introductory DLMS note 5f.

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. Express the originating

activity's time of transaction set preparation

in UTC.

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

format.

3. Authorized DLMS enhancement; see

introductory DLMS note 5f.

O TM 4/8 Used 1

BIA06 306 Action Code

Description: Code indicating type of action

O ID 1/2 Used 1

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

Code Name

FI File

DLMS Note:

1. Authorized for Air Force contractor inventory control point (CICP) use to provide an image of the LR

transfer/decapitalization transaction to the Air Force accountable property system record (APSR), only

when CICP is providing the APSR an image of a transaction which the CICP received from an external

system. There will be no 2/N106/450 code TO for this transaction image. Refer to ADC 1232.

2. Authorized for DAAS use when DAAS creates an image for the Air Force APSR, of a transaction

which the Air Force CICP sent to a GIM or LIM. DAAS creates the image when CICP sends an 846D

transaction to an external system other than the APSR and include 2/N101/450/ZD and 2/N106/450/PK.

There will be no 2/N106/450 code TO for this transaction image. Refer to ADC 1232.

1. Authorized for Air Force contractor inventory control point (CICP) use to provide an image of the LR

transfer/decapitalization transaction to the Air Force accountable property system record (APSR), only

when CICP is providing the APSR an image of a transaction which the CICP received from an external

system. There will be no 2/N106/450 code TO for this transaction image. Refer to ADC 1232.

2. Authorized for DAAS use when DAAS creates an image for the Air Force APSR, of a transaction

which the Air Force CICP sent to a GIM or LIM. DAAS creates the image when CICP sends an 846D

transaction to an external system other than the APSR and include 2/N101/450/ZD and 2/N106/450/PK.

There will be no 2/N106/450 code TO for this transaction image. Refer to ADC 1232.
DLMS Implementation Convention (IC) 846S Logistics Reassignment Storage

Information Order/Reply

ADC 66, 77, 151, 260, 436, 1043C, 1232, 1254, 1367 and 1412 

DLM 4000.25

004010F846S2SA09 8 March 8, 2022

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. 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 the 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 code SB or

ZN.

2. The following codes are authorized.

M ID 2/3 Must use 1

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

Code Name

SB Storage Area

DLMS Note:

Use to identify a depot or other storage activity.

ZN Losing Inventory Manager

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

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

Code Name

10 Department of Defense Activity Address Code (DODAAC)

DLMS Note:

DLMS enhancement; see introductory DLMS note 5a.

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
DLMS Implementation Convention (IC) 846S Logistics Reassignment Storage

Information Order/Reply

ADC 66, 77, 151, 260, 436, 1043C, 1232, 1254, 1367 and 1412 

DLM 4000.25

004010F846S2SA09 9 March 8, 2022

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

Code Name

FR Message From

DLMS Note:

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

the transaction set.
DLMS Implementation Convention (IC) 846S Logistics Reassignment Storage

Information Order/Reply

ADC 66, 77, 151, 260, 436, 1043C, 1232, 1254, 1367 and 1412 

DLM 4000.25

004010F846S2SA09 10 March 8, 2022

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.

DLMS Note:

Must use this 1/LM/140 loop to identify coded information used 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) 846S Logistics Reassignment Storage

Information Order/Reply

ADC 66, 77, 151, 260, 436, 1043C, 1232, 1254, 1367 and 1412 

DLM 4000.25

004010F846S2SA09 11 March 8, 2022

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

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

Code Name

0 Document Identification Code

DLMS Note:

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

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.

A9 Supplemental Data

DLMS Note:

1. Use to identify supplemental address/data.

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

Supplemental Address (SUPAAD) field. During this time, field size is restricted to 6 positions; see

introductory DLMS note 5d.

3. Expanded use of this field for supplemental data with out size restriction is a DLMS enhancement;

see introductory DLMS note 5a.

4. Under full DLMS, the requirement to pass activity address information within the supplement data

field will be streamlined. Activity address data previously contained in the SUPAAD will be reflected

exclusively in the N1 segment. Future streamlined data; see introductory DLMS note 5c.

1. Use to identify supplemental address/data.

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

Supplemental Address (SUPAAD) field. During this time, field size is restricted to 6 positions; see

introductory DLMS note 5d.

3. Expanded use of this field for supplemental data with out size restriction is a DLMS enhancement;

see introductory DLMS note 5a.

4. Under full DLMS, the requirement to pass activity address information within the supplement data

field will be streamlined. Activity address data previously contained in the SUPAAD will be reflected

exclusively in the N1 segment. Future streamlined data; see introductory DLMS note 5c.

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

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) 846S Logistics Reassignment Storage

Information Order/Reply

ADC 66, 77, 151, 260, 436, 1043C, 1232, 1254, 1367 and 1412 

DLM 4000.25

004010F846S2SA09 12 March 8, 2022

LIN Item Identification Pos: 010 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:

Must use the 2/LIN/010 loop to identify the National Stock Number (NSN), transaction number, and inventory information.

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

authorized.

M ID 2/2 Must use 1

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

Code Name

F4 Series Identifier

DLMS Note:

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

FS National Stock Number

MG Manufacturer's Part Number

MN Model Number

DLMS Note:

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

SN Serial Number

DLMS Note:
DLMS Implementation Convention (IC) 846S Logistics Reassignment Storage

Information Order/Reply

ADC 66, 77, 151, 260, 436, 1043C, 1232, 1254, 1367 and 1412 

DLM 4000.25

Code Name

004010F846S2SA09 13 March 8, 2022

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

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)

DLMS Note: The following codes are

authorized.

X ID 2/2 Used 1

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

Code Name

ZB Commercial and Government Entity (CAGE) Code

DLMS Note:

Use with LIN02 to uniquely identify a manufacturers 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) 846S Logistics Reassignment Storage

Information Order/Reply

ADC 66, 77, 151, 260, 436, 1043C, 1232, 1254, 1367 and 1412 

DLM 4000.25

004010F846S2SA09 14 March 8, 2022

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:

Use multiple repetitions of this segment to define unique dates associated with the transaction.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

DTM01 374 Date/Time Qualifier

Description: Code specifying type of date

or time, or both date and time

DLMS Note: The following codes are

authorized.

M ID 3/3 Must use 1

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

Code Name

007 Effective

DLMS Note:

Must use for LR storage information order transactions to identify the Effective Transfer Date (ETD);

otherwise, do not use.

097 Transaction Creation

DLMS Note:

1. Use to identify the transaction preparation date. Correspond date to the Universal Time Coordinate

(UTC).

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

DTM02 373 Date

Description: Date expressed as

CCYYMMDD

X DT 8/8 Used 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

(Transaction Creation) to provide the time

associated with the transaction preparation

date. 

2. Express time in UTC using a

four-position (HHMM) format. 

3. Authorized DLMS enhancement; see

introductory DLMS note 5f on IC cover

page.

X TM 4/8 Used 1
DLMS Implementation Convention (IC) 846S Logistics Reassignment Storage

Information Order/Reply

ADC 66, 77, 151, 260, 436, 1043C, 1232, 1254, 1367 and 1412 

DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F846S2SA09 15 March 8, 2022
DLMS Implementation Convention (IC) 846S Logistics Reassignment Storage

Information Order/Reply

ADC 66, 77, 151, 260, 436, 1043C, 1232, 1254, 1367 and 1412 

DLM 4000.25

004010F846S2SA09 16 March 8, 2022

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:

Must use at least one repetition to identify the document number. Use additional repetitions as needed.

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

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

Code Name

6L Agent Contract Number

DLMS Note:

1. Air Force uses for Air Force GFP accountability transactions to identify the procurement instrument

identifier (PIID) applicable to the contract authorizing Air Force CICP 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 this field.

3. Required for Air Force GFP accountability. 

4. Authorized DLMS enhancement. Refer to ADC 1232.

1. Air Force uses for Air Force GFP accountability transactions to identify the procurement instrument

identifier (PIID) applicable to the contract authorizing Air Force CICP 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 this field.

3. Required for Air Force GFP accountability. 

4. Authorized DLMS enhancement. Refer to ADC 1232.

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

TN Transaction Reference Number

DLMS Note:

Use to identify the document number.

W8 Suffix

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
DLMS Implementation Convention (IC) 846S Logistics Reassignment Storage

Information Order/Reply

ADC 66, 77, 151, 260, 436, 1043C, 1232, 1254, 1367 and 1412 

DLM 4000.25

004010F846S2SA09 17 March 8, 2022

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.

DLMS Note:

Use multiple iterations of the 2/QTY/320 loop when exchanging asset status information to stratify quantities by materiel classification.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

QTY01 673 Quantity Qualifier

Description: Code specifying the type of

quantity

DLMS Note: The following codes are

authorized.

M ID 2/2 Must use 1

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

Code Name

RY Requirement Quantity

DLMS Note:

Army uses for intra-Army LR in LR storage information order transactions, to identify quantity to be

transferred to the SICA to fill open requirements. The distribution depot uses in LR storage information

reply transactions to identify the quantity transferred to the Army SICA. Use of this data is meaningful

to Army and DLA DSS only. For intra-Army LR under DLSS, this data is cited in multiuse rp 51-55 of

MILSTRAP DIC DZC and DZD Authorized Army/DLA DSS DLMS migration enhancement for use in

intra-Army LR.

Army uses for intra-Army LR in LR storage information order transactions, to identify quantity to be

transferred to the SICA to fill open requirements. The distribution depot uses in LR storage information

reply transactions to identify the quantity transferred to the Army SICA. Use of this data is meaningful

to Army and DLA DSS only. For intra-Army LR under DLSS, this data is cited in multiuse rp 51-55 of

MILSTRAP DIC DZC and DZD Authorized Army/DLA DSS DLMS migration enhancement for use in

intra-Army LR.

V1 Retention Quantity

DLMS Note:

Use to identify the retention quantity. For LR storage information order transactions this represents the

quantity scheduled to be retained by the LIM. For LR storage information reply transactions this

represents the quantity actually retained by the LIM. Do not use in reply transactions if no

corresponding order transaction was received.

V2 Available Quantity

DLMS Note:

1. Use for LR storage information reply transactions to identify the quantity transferred to GIM

ownership; otherwise, do not use. The quantity available for transfer is subject to the retention quantity

cited in the LR storage information order. 

2. To reverse all or part of a previously submitted LR storage information reply, use a minus sign in

front of the quantity to be reversed.

V3 Transfer Quantity

DLMS Note:

Use for LR storage information order transactions to identify the quantity to be transferred to GIM

ownership; otherwise, do not use. To reverse all or part of an LR storage information order, use a minus

sign in front of the quantity to be reversed.

QTY02 380 Quantity

Description: Numeric value of quantity

DLMS Note: 1. Express as a number with

X R 1/15 Used 1
DLMS Implementation Convention (IC) 846S Logistics Reassignment Storage

Information Order/Reply

ADC 66, 77, 151, 260, 436, 1043C, 1232, 1254, 1367 and 1412 

DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F846S2SA09 18 March 8, 2022

no decimals.

2. A field size exceeding 5 positions (seven

for FSG 13, ammunition) may not be

received or understood by recipient's

automated processing system. See

introductory DLMS note 5d.

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

manner in which a measurement has been

taken

DLMS Note: 1. Use to accommodate

legacy system requirements.

2. DLMS users see the DLMS Unit of Issue

and Purchase Unit Conversion Table for

available codes. 

M ID 2/2 Must use 1
DLMS Implementation Convention (IC) 846S Logistics Reassignment Storage

Information Order/Reply

ADC 66, 77, 151, 260, 436, 1043C, 1232, 1254, 1367 and 1412 

DLM 4000.25

004010F846S2SA09 19 March 8, 2022

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.

DLMS Note:

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

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

Code Name

DF Department of Defense (DoD)
DLMS Implementation Convention (IC) 846S Logistics Reassignment Storage

Information Order/Reply

ADC 66, 77, 151, 260, 436, 1043C, 1232, 1254, 1367 and 1412 

DLM 4000.25

004010F846S2SA09 20 March 8, 2022

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

5a.

DLMS Note: 1. Use either code 99 or A1

(but not both), except for ammunition where

both codes may be used. Use of both

codes for ammunition is a DLMS

enhancement; see introductory DLMS note

5a.

2. The following codes are authorized. 

(Use of both codes for ammunition is a

DLMS enhancement (see introductory

DLMS note 5a. )

O ID 1/3 Used 1

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

Code Name

78 Project Code

83 Supply Condition Code

84 Management Code

87 Subsistence Type of Pack Code

DLMS Note:

Use for subsistence items to identify

subsistence type of pack information.

99 Purpose Code

A1 Ownership Code

A9 Supplemental Data

DLMS Note:

1. Use to identify supplemental address/data.

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

Supplemental Address (SUPAAD) field. During this time, field size is restricted to 6 positions; see

introductory DLMS note 5d.

3. Expanded use of this field for supplemental data with out size restriction is a DLMS enhancement;

see introductory DLMS note 5a.

4. Under full DLMS, the requirement to pass activity address information within the supplement data

field will be streamlined. Activity address data previously contained in the SUPAAD will be reflected

exclusively in the N1 segment. Future streamlined data; see introductory DLMS note 5c.

1. Use to identify supplemental address/data.

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

Supplemental Address (SUPAAD) field. During this time, field size is restricted to 6 positions; see

introductory DLMS note 5d.

3. Expanded use of this field for supplemental data with out size restriction is a DLMS enhancement;

see introductory DLMS note 5a.

4. Under full DLMS, the requirement to pass activity address information within the supplement data

field will be streamlined. Activity address data previously contained in the SUPAAD will be reflected

exclusively in the N1 segment. Future streamlined data; see introductory DLMS note 5c.

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 5a.
DLMS Implementation Convention (IC) 846S Logistics Reassignment Storage

Information Order/Reply

ADC 66, 77, 151, 260, 436, 1043C, 1232, 1254, 1367 and 1412 

DLM 4000.25

Code Name

004010F846S2SA09 21 March 8, 2022

GQ Group Qualifier Code

DLMS Note:

Use to identify the MMAC for NSNs to be managed by a specific manager (i.e., system, program,

aggregation, selected FSC, technology group). This is an Air Force-unique data element, meaningful to

the Air Force only. Non-Air Force Components perpetuate without action.

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

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

23-110, Volumes 1 and 2.

Use to identify the MMAC for NSNs to be managed by a specific manager (i.e., system, program,

aggregation, selected FSC, technology group). This is an Air Force-unique data element, meaningful to

the Air Force only. Non-Air Force Components perpetuate without action.

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

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

23-110, Volumes 1 and 2.

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) 846S Logistics Reassignment Storage

Information Order/Reply

ADC 66, 77, 151, 260, 436, 1043C, 1232, 1254, 1367 and 1412 

DLM 4000.25

004010F846S2SA09 22 March 8, 2022

N1 Name Pos: 450 Max: 1

Detail - Optional

Loop: N1 Elements: 4

User Option (Usage): Used

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

Syntax Rules: 

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

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

Comments: 

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

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

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

DLMS Note:

Must use this 2/N1/450 loop to identify the organization to receive 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 SB

or ZN.

2. The following codes are authorized.

M ID 2/3 Must use 1

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

Code Name

55 Service Manager

DLMS Note:

Army uses for intra-Army LR to identify the Secondary Inventory Control Activity (SICA) as an

authorized user of the materiel. When there are less assets available than indicated in the LR storage

information order, Army requires that the SICA quantity be filled prior to the Army GIM transfer quantity. 

Use of this data is meaningful to Army and DLA DSS only. Army cites data in multiuse rp 48-50 of

MILSTRAP DIC DZC and DZD. Authorized Army/DLA DSS DLMS migration enhancement for

intra-Army LR use.

A data maintenance action was approved in version 4030. The approved code/name is

“SIC-Secondary Inventory Control Activity”.

Army uses for intra-Army LR to identify the Secondary Inventory Control Activity (SICA) as an

authorized user of the materiel. When there are less assets available than indicated in the LR storage

information order, Army requires that the SICA quantity be filled prior to the Army GIM transfer quantity. 

Use of this data is meaningful to Army and DLA DSS only. Army cites data in multiuse rp 48-50 of

MILSTRAP DIC DZC and DZD. Authorized Army/DLA DSS DLMS migration enhancement for

intra-Army LR use.

A data maintenance action was approved in version 4030. The approved code/name is

“SIC-Secondary Inventory Control Activity”.

SB Storage Area

DLMS Note:

Use to identify a depot or other storage activity.

ZD Party to Receive Reports

DLMS Note:

Authorized for use for Air Force GFP accountability to identify the Air Force program manager in the

accountable property system of record (APSR) when the contractor inventory control point (CICP) must

report an image of this transaction to a separately maintained property system. Must identify the

program manager by RIC (2/N103 qualifier M4). If the program manager DoDAAC does not have an

assigned RIC, use the generic Air Force GFP APSR RIC with 2/N106=PK and use a second iteration of

the N1 loop (repeating Code ZD without 2/N106=PK) to provide the program manager DoDAAC. Use in

conjunction with N106 Code PK to provide an image of the transaction (image is identified by

1/BIA06/020 Action Code FI) to update the APSR associated with the CICP (identified in 1/N101/080).

Refer to ADC 1232. 

Authorized for use for Air Force GFP accountability to identify the Air Force program manager in the

accountable property system of record (APSR) when the contractor inventory control point (CICP) must

report an image of this transaction to a separately maintained property system. Must identify the

program manager by RIC (2/N103 qualifier M4). If the program manager DoDAAC does not have an

assigned RIC, use the generic Air Force GFP APSR RIC with 2/N106=PK and use a second iteration of

the N1 loop (repeating Code ZD without 2/N106=PK) to provide the program manager DoDAAC. Use in

conjunction with N106 Code PK to provide an image of the transaction (image is identified by

1/BIA06/020 Action Code FI) to update the APSR associated with the CICP (identified in 1/N101/080).

Refer to ADC 1232. 

ZN Losing Inventory Manager

ZP Gaining Inventory Manager
DLMS Implementation Convention (IC) 846S Logistics Reassignment Storage

Information Order/Reply

ADC 66, 77, 151, 260, 436, 1043C, 1232, 1254, 1367 and 1412 

DLM 4000.25

Code Name

004010F846S2SA09 23 March 8, 2022

DLMS Note:

Use only for LR storage ownership transfer order transactions to identify the GIM. Do not use when

reversing a previously submitted transaction.

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

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

Code Name

10 Department of Defense Activity Address Code (DODAAC)

DLMS Note:

DLMS enhancement; see introductory DLMS note 5a.

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

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

Code Name

PK Party to Receive Copy

DLMS Note:

Authorized for Air Force GFP accountability use with N101Code ZD to provide an image of an LR

Storage Information Order/Reply transaction to the APSR. Do not use N106 Code TO with Air Force

CICP transaction image sent to the APSR.

TO Message To

DLMS Note:

Must use with 2/N101/450 codes SB or ZN to indicate the organization cited in N104 is to receive the

transaction.
DLMS Implementation Convention (IC) 846S Logistics Reassignment Storage

Information Order/Reply

ADC 66, 77, 151, 260, 436, 1043C, 1232, 1254, 1367 and 1412 

DLM 4000.25

004010F846S2SA09 24 March 8, 2022

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