DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

004010F869A3AA16 1 September 22, 2023

869 Order Status Inquiry

Functional Group=RS

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Order Status Inquiry Transaction Set

(869) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to request all pertinent

information relative to an entire purchase order, selected line items on a purchase order, or selected products/services on a purchase order.

Inquiry can also be made for all or a selected portion of the customer's ordered items, all or a selected portion of the customer's unshipped

items, or all or a selected portion of the customer's shipped items.

DLMS Note:

1a. Organizations use this transaction set to inquire about the status of or request supply assistance for previously submitted requisitions. 

Organizations may also use this transaction to request shipment tracing on registered insured, and certified parcel post. Use a single

occurrence of this transaction set to exchange single or multiple transactions between a single activity and a single supply source 

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

2. This DLMS Implementation Convention contains:

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

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

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

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

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

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

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

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

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

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

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

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

DEDSO prior to use.

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

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

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

- ADC 50, Revision to DLMS Supplement (DS) 869A, Requisition Inquiry/Supply Assistance Request

- ADC 59, Customer Identification on Automated exception Requisitions

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

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

- ADC 88, DLMS Mapping for MILSTRIP DI Code AFT, Request for Shipment Tracing on Registered Insured, and Certified Parcel Post. 

- ADC 92, Qualifier Additions to Segment FA2,

- ADC 94, Revision to DLMS Supplement 869A, for Inclusion of Shipment Status for Open Requisitions

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

(IMSP)

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

(IMSP)

- ADC 304, AFY Material Identification and Quantity Mapping to DLMS 869A, Requisition Inquiry/Supply Assistance Request

- ADC 326, DLMS Supplement (DS) 869A, Requisition Inquiry/Supply Assistance Request, Correction and Clarification of Data Mapping,

Administrative Updates, and Coordination of Procedures for Transaction-Based Supply Assistances Requests

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

Consumable Support Materiel

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

BRAC SS&D/IMSP

- ADC 388, Automated Method of Detecting System Downtime or Excessive Processing Times in Air Force BRAC SS&D/IMSP Expedited

Requisition Process and Associated Dual Function Materiel Release Order (MRO) Process

- ADC 435, DLMS Revisions for SFIS Compliance

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

1a. Organizations use this transaction set to inquire about the status of or request supply assistance for previously submitted requisitions. 

Organizations may also use this transaction to request shipment tracing on registered insured, and certified parcel post. Use a single

occurrence of this transaction set to exchange single or multiple transactions between a single activity and a single supply source 

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

2. This DLMS Implementation Convention contains:

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

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

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

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

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

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

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

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

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

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

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

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

DEDSO prior to use.

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

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

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

- ADC 50, Revision to DLMS Supplement (DS) 869A, Requisition Inquiry/Supply Assistance Request

- ADC 59, Customer Identification on Automated exception Requisitions

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

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

- ADC 88, DLMS Mapping for MILSTRIP DI Code AFT, Request for Shipment Tracing on Registered Insured, and Certified Parcel Post. 

- ADC 92, Qualifier Additions to Segment FA2,

- ADC 94, Revision to DLMS Supplement 869A, for Inclusion of Shipment Status for Open Requisitions

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

(IMSP)

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

(IMSP)

- ADC 304, AFY Material Identification and Quantity Mapping to DLMS 869A, Requisition Inquiry/Supply Assistance Request

- ADC 326, DLMS Supplement (DS) 869A, Requisition Inquiry/Supply Assistance Request, Correction and Clarification of Data Mapping,

Administrative Updates, and Coordination of Procedures for Transaction-Based Supply Assistances Requests

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

Consumable Support Materiel

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

BRAC SS&D/IMSP

- ADC 388, Automated Method of Detecting System Downtime or Excessive Processing Times in Air Force BRAC SS&D/IMSP Expedited

Requisition Process and Associated Dual Function Materiel Release Order (MRO) Process

- ADC 435, DLMS Revisions for SFIS Compliance

- ADC 1009A, DLMS Enhancements for Requisitioning to Improve Use of Mark-for Addressing, Expand Authorized Priority Designator 
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

004010F869A3AA16 2 September 22, 2023

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

Purchase/Credit Card Payment

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

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

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

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

Code

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

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

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

- Administrative Update to Reflect Realignment to Recognize DLMS Program Office Completed on January 26, 2017

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

September 28, 2018

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

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

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

- ADC 1383, Deletion of Unused Qualifier Related to Transportation/Method Codes

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

Office (DEDSO) - Completed on March 15, 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

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

Purchase/Credit Card Payment

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

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

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

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

Code

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

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

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

- Administrative Update to Reflect Realignment to Recognize DLMS Program Office Completed on January 26, 2017

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

September 28, 2018

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

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

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

- ADC 1383, Deletion of Unused Qualifier Related to Transportation/Method Codes

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

Office (DEDSO) - Completed on March 15, 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 BSI Beginning Segment for Order

Status Inquiry

M 1 Must use

* 30 NTE Note/Special Instruction O 100 Not Used

Detail:

Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - HL LOOP ID - HL >1

10 HL Hierarchical Level M 1 Must use

* 20 PRF Purchase Order Reference O 1 Not Used

30 DTM Date/Time Reference O 10 Used

50 LIN Item Identification O >1 Used

60 PID Product/Item Description O 1000 Used

* 70 MEA Measurements O 40 Not Used

80 QTY Quantity O 1 Used

* 100 GF Furnished Goods and Services O 1 Not Used

LOOP ID - REF LOOP ID - REF >1

105 REF Reference Identification O 1 Used

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

LOOP ID - N1 LOOP ID - N1 >1

110 N1 Name O 1 Used

* 120 N2 Additional Name Information O 2 Not Used

* 130 N3 Address Information O 2 Not Used

* 140 N4 Geographic Location O 1 Not Used

* 150 REF Reference Identification O 12 Not Used

160 PER Administrative Communications

Contact

O 3 Used

LOOP ID - LM LOOP ID - LM >1

170 LM Code Source Information O 1 Used

180 LQ Industry Code M >1 Must use

LOOP ID - FA1 LOOP ID - FA1 >1

190 FA1 Type of Financial Accounting Data O 1 Used

200 FA2 Accounting Data M >1 Must use
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

004010F869A3AA16 3 September 22, 2023

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: 

3/10 CTT01 is the number of HL segments.
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

004010F869A3AA16 4 September 22, 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

Code Name

869 Order Status Inquiry

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) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

004010F869A3AA16 5 September 22, 2023

BSI Beginning Segment for Order Status

Inquiry

Pos: 20 Max: 1

Heading - Mandatory

Loop: N/A Elements: 7

User Option (Usage): Must use

Purpose: To indicate the beginning of an order status inquiry and provide the type of customer status inquiry

Semantics: 

1. BSI01 is a status inquiry reference number.

2. BSI02 is date of the inquiry.

3. BSI06 is time of the inquiry.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

BSI01 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

BSI02 373 Date

Description: Date expressed as

CCYYMMDD

DLMS Note: This date corresponds to the

date of transaction set preparation

expressed as the Universal Time

Coordinate (UTC).

M DT 8/8 Must use 1

BSI03 847 Order/Item Code

Description: Code identifying a group of

orders and items

M ID 1/2 Must use 1

Code Name

PI Selected Orders - Shipped Orders

DLMS Note:

1. Use to indicate that the transaction set contains transactions that apply to requisitions for which

shipment status has been received.

2. Use for requests for shipment tracing.

3. Used during legacy MILSTRIP/DLMS transition period when transaction contains a request for

identification of the initial transportation shipping activity.

1. Use to indicate that the transaction set contains transactions that apply to requisitions for which

shipment status has been received.

2. Use for requests for shipment tracing.

3. Used during legacy MILSTRIP/DLMS transition period when transaction contains a request for

identification of the initial transportation shipping activity.

PO Selected Orders - Unshipped Items

DLMS Note:

1. Use to indicate that the transaction set contains transactions that apply to open requisitions for which

shipment status has not been received.

2. Use for requisition follow-ups including requests for improved ESD.

3. Use for supply assistance requests. DLMS enhancement; see introductory DLMS note 2a. 

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

O TM 4/8 Must use 1
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F869A3AA16 6 September 22, 2023

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.

BSI07 353 Transaction Set Purpose Code

Description: Code identifying purpose of

transaction set

O ID 2/2 Must use 1

Code Name

00 Original

42 Temporary Record

DLMS Note:

Use as a Downtime Detection Indicator to alert processing systems that this requisition query is used

for system testing to determine elapsed response time between the query and the responding supply

status. This transaction contains a pseudo document number. Authorized DLMS enhancement by

agreement with DLA only. Refer to ADC 388.

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.

BSI08 640 Transaction Type Code

Description: Code specifying the type of

transaction

O ID 2/2 Must use 1

Code Name

71 Filing and Search Request

DLMS Note:

Use (in conjunction with BSI03=PI, Shipped Orders) to identify requests for shipment tracing -

registered, insured, and certified U.S. Postal Service. (This corresponds to MILSTRIP Document

Identifier AFT.)

AF Requisition Follow-Up

DLMS Note:

1. Use (in conjunction with BSI03=PO, Unshipped Orders) to identify requisition follow-ups for status on

previously submitted requisitions. (This corresponds to MILSTRIP Document Identifier AF1-AF5.)

2. Use (in conjunction with BSI03=PO, Unshipped Orders to identify the requisition follow-up requests

for improved estimated shipping date (ESD). (This corresponds to MILSTRIP Document Identifier AFC).

 When provided for this purpose, must be used in combination with PID05, Code 2.

 3. Use (in conjunction with BSI03=PI, Shipped Orders) to identify requisition follow-up requests for

DoDAAC of initial transportation shipping activity (This corresponds to MILSTRIP Document Identifier

AFY). When provided for this purpose, must be used in combination with PID05, Code 1. The Request

for DoDAAC of Initial Transportation Shipping Activity transaction is applicable in a mixed DLMS/MILS

environment where a separate transaction is needed to provide the requested information. Under

DLMS, the distribution depot identifies the shipping activity in the shipment status transaction,

eliminating the need for a follow-up.

1. Use (in conjunction with BSI03=PO, Unshipped Orders) to identify requisition follow-ups for status on

previously submitted requisitions. (This corresponds to MILSTRIP Document Identifier AF1-AF5.)

2. Use (in conjunction with BSI03=PO, Unshipped Orders to identify the requisition follow-up requests

for improved estimated shipping date (ESD). (This corresponds to MILSTRIP Document Identifier AFC).

 When provided for this purpose, must be used in combination with PID05, Code 2.

 3. Use (in conjunction with BSI03=PI, Shipped Orders) to identify requisition follow-up requests for

DoDAAC of initial transportation shipping activity (This corresponds to MILSTRIP Document Identifier

AFY). When provided for this purpose, must be used in combination with PID05, Code 1. The Request

for DoDAAC of Initial Transportation Shipping Activity transaction is applicable in a mixed DLMS/MILS

environment where a separate transaction is needed to provide the requested information. Under

DLMS, the distribution depot identifies the shipping activity in the shipment status transaction,

eliminating the need for a follow-up.
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

Code Name

004010F869A3AA16 7 September 22, 2023

AR Supply Assistance

DLMS Note:

1. Use (in conjunction with BSI03=PO), Unshipped Orders) to identify requests for supply assistance

(improved support) for requisitions meeting specific criteria for priority (Priority Designator 01-08) and

receipt of open supply status. (This establishes a transaction-based process comparable to the

MILSTRIP procedures for Supply Assistance Request currently prepared as a message, e-mail, or

telephonic request. There is no comparable MILSTRIP transaction.)

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

1. Use (in conjunction with BSI03=PO), Unshipped Orders) to identify requests for supply assistance

(improved support) for requisitions meeting specific criteria for priority (Priority Designator 01-08) and

receipt of open supply status. (This establishes a transaction-based process comparable to the

MILSTRIP procedures for Supply Assistance Request currently prepared as a message, e-mail, or

telephonic request. There is no comparable MILSTRIP transaction.)

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

BSI09 306 Action Code

Description: Code indicating type of action

O ID 1/2 Used 1

Code Name

83 Future

DLMS Note:

1. Used by Navy industrial activities (IAs) to identify a Requisition Inquiry/Supply Assistance Request on

a Requisition Alert allowing stock positioning or procurement action in response to the forecasted future

funded requirement. The requisition alert is an unfunded requirement.

2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

004010F869A3AA16 8 September 22, 2023

HL Hierarchical Level Pos: 10 Max: 1

Detail - Mandatory

Loop: HL Elements: 3

User Option (Usage): Must use

Purpose: To identify dependencies among and the content of hierarchically related groups of data segments

Comments: 

1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment

data, and packaging data to line-item data.

2. The HL segment defines a top-down/left-right ordered structure.

3. HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01

could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL

segment and would be incremented by one in each subsequent HL segment within the transaction.

4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.

5. HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in

the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring

to shipment, order, or item-level information.

6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

DLMS Note:

1. The transaction set hierarchical data structure is address information followed by transaction specific information and, as required,

substitute item loops.

2. Use the first 2/HL/010 loop iteration to identify address information.

3. Use multiple 2/HL/010 transaction loops as needed for each 2/HL/010 address loop to identify individual transactions subject to inquiry or

assistance and their associated data.

4. Use multiple 2/HL/010 substitute item loops in supply assistance transactions only as needed for each 2/HL/010 transaction loop to

identify acceptable substitute items.

1. The transaction set hierarchical data structure is address information followed by transaction specific information and, as required,

substitute item loops.

2. Use the first 2/HL/010 loop iteration to identify address information.

3. Use multiple 2/HL/010 transaction loops as needed for each 2/HL/010 address loop to identify individual transactions subject to inquiry or

assistance and their associated data.

4. Use multiple 2/HL/010 substitute item loops in supply assistance transactions only as needed for each 2/HL/010 transaction loop to

identify acceptable substitute items.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

HL01 628 Hierarchical ID Number

Description: A unique number assigned by

the sender to identify a particular data

segment in a hierarchical structure

DLMS Note: In the first 2/HL/010 loop

iteration, cite 1. In each subsequent loop

iteration, increase incrementally by 1.

M AN 1/12 Must use 1

HL02 734 Hierarchical Parent ID Number

Description: Identification number of the

next higher hierarchical data segment that

the data segment being described is

subordinate to

DLMS Note: 1. Must use in every 2/HL/010

transaction loop iteration to identify the

address loop with which the current loop is

associated. Data element content is the

sequential number assigned to the

2/HL/010 address loop iteration and serves

as the cross-reference between transaction

set level organization data and associated

transactions.

DLMS Note: 1. Must use in every 2/HL/010

transaction loop iteration to identify the

address loop with which the current loop is

associated. Data element content is the

sequential number assigned to the

2/HL/010 address loop iteration and serves

as the cross-reference between transaction

set level organization data and associated

transactions.

2. Must use in every 2/HL/010 substitute

item loop iteration to identify the transaction

loop with which the current loop is

associated. Data element content is the

sequential number assigned to the 

O AN 1/12 Used 1
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F869A3AA16 9 September 22, 2023

2/HL/010 transaction loop iteration and

serves as the cross-reference between the

transaction and acceptable substitute items.

HL03 735 Hierarchical Level Code

Description: Code defining the

characteristic of a level in a hierarchical

structure

M ID 1/2 Must use 1

Code Name

V Address Information

DLMS Note:

1. Use in every 2/HL/010 address loop iteration.

2. Use to identify the organization originating and the organization to receive the transaction set.

W Transaction Reference Number

DLMS Note:

1. Use in every 2/HL/010 transaction loop iteration.

2. Use to identify the original requisition and associated data content.

SB Substitute

DLMS Note:

1. Use in every 2/HL/010 substitute item loop iteration for supply assistance transactions only.

2. DLMS enhancement; see introductory DLMS note 2a.
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

004010F869A3AA16 10 September 22, 2023

DTM Date/Time Reference Pos: 30 Max: 10

Detail - Optional

Loop: HL Elements: 2

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 only in the 2/HL/010 transaction loops.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

DTM01 374 Date/Time Qualifier

Description: Code specifying type of date

or time, or both date and time

M ID 3/3 Must use 1

Code Name

168 Release

DLMS Note:

Use for requests for shipment tracing to identify the date materiel was released to the carrier. 

DTM02 373 Date

Description: Date expressed as

CCYYMMDD

X DT 8/8 Used 1
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

004010F869A3AA16 11 September 22, 2023

LIN Item Identification Pos: 50 Max: >1

Detail - Optional

Loop: HL Elements: 10

User Option (Usage): Used

Purpose: To specify basic item identification data

Syntax Rules: 

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Semantics: 

1. LIN01 is the line item identification

Comments: 

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

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

ISBN No., Model No., or SKU.

DLMS Note:

1. Use in all 2/HL/010 transaction loop iterations in supply assistance requests to identify and provide amplifying information about the

requisitioned materiel.

2. Use in all 2/HL/010 transaction loop iterations in requisition followups to identify the requisitioned materiel.

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. Use only one of codes A2,

A4, FB, FS, MG, SW, YP, or ZZ to identify

the materiel as indicated in the most recent

status transaction.

2. For requests for shipment tracing, use

the materiel identification provided in the

shipment status.

M ID 2/2 Must use 1

Code Name

A2 Department of Defense Identification Code (DoDIC)

DLMS Note:

Use to identify ammunition items.

A4 Subsistence Identification Number
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

Code Name

004010F869A3AA16 12 September 22, 2023

DLMS Note:

Use to identify subsistence items.

F4 Series Identifier

DLMS Note:

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

FB Form Number

DLMS Note:

Use to identify the form stock number.

FS National Stock Number

DLMS Note:

1. Use to identify the NSN. 

2. When the Unit of Use Indicator is included (BSI07=ZZ), the NSN will be interpreted as a unit of use

requirement. Unit of use is an authorized DLMS enhancement under DLA industrial activity support

agreement.

FT Federal Supply Classification

DLMS Note:

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

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

MG Manufacturer's Part Number

DLMS Note:

1. Use to identify nonstandard materiel. 

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

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

MN Model Number

DLMS Note:

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

SN Serial Number

DLMS Note:

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

SW Stock Number

DLMS Note:

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

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

YP Publication Number

DLMS Note:

Use to identify the publication stock number.

ZZ Mutually Defined

DLMS Note:

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

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

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

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: 1. Use codes EM for weapon

system application, F8 for next higher

assembly, and W1 for the end item serial

X ID 2/2 Used 1
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F869A3AA16 13 September 22, 2023

number, as needed, on a supply assistance

request to indicate amplifying information

associated with the requisitioned materiel. 

DLMS enhancement; see introductory

DLMS note 2a.

2. Use data element 235/234 pairs to

identify data pertinent to the transaction. 

Present the information in any selected

order. Unless otherwise specified, the

multiple codes listed for a single qualifier

data element identify the range of possible

data requirements. When needed, use the

next available combination of data element

235/234 pairs to provide the necessary

data.

2. Use data element 235/234 pairs to

identify data pertinent to the transaction. 

Present the information in any selected

order. Unless otherwise specified, the

multiple codes listed for a single qualifier

data element identify the range of possible

data requirements. When needed, use the

next available combination of data element

235/234 pairs to provide the necessary

data.

Code Name

CN Commodity Name

DLMS Note:

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

EM Equipment Identification Number

DLMS Note:

Use to identify the weapon system application associated with the requisitioned materiel.

F8 Next Higher Used Assembly

DLMS Note:

Use to identify the NHA associated with the requisitioned materiel.

W1 End Item Serial Number

DLMS Note:

Use to identify the serial number of the end-item associated with the requisitioned materiel.

ZB Commercial and Government Entity (CAGE) Code

DLMS Note:

1. Use with LIN02 code MG to uniquely identify a manufacturer's (or supplier’s) part number.

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

Advantage/Global internet order from a vendor catalog.

LIN05 234 Product/Service ID

Description: Identifying number for a

product or service

X AN 1/48 Used 1

LIN06 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

LIN07 234 Product/Service ID

Description: Identifying number for a

product or service

X AN 1/48 Used 1

LIN08 235 Product/Service ID Qualifier

Description: Code identifying the

type/source of the descriptive number used

in Product/Service ID (234)

X ID 2/2 Used 1

LIN09 234 Product/Service ID

Description: Identifying number for a

product or service

X AN 1/48 Used 1

LIN10 235 Product/Service ID Qualifier X ID 2/2 Used 1
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F869A3AA16 14 September 22, 2023

Description: Code identifying the

type/source of the descriptive number used

in Product/Service ID (234)

LIN11 234 Product/Service ID

Description: Identifying number for a

product or service

X AN 1/48 Used 1
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

004010F869A3AA16 15 September 22, 2023

PID Product/Item Description Pos: 60 Max: 1000

Detail - Optional

Loop: HL Elements: 2

User Option (Usage): Used

Purpose: To describe a product or process in coded or free-form format

Syntax Rules: 

1. C0403 - If PID04 is present, then PID03 is required.

2. R0405 - At least one of PID04 or PID05 is required.

3. C0703 - If PID07 is present, then PID03 is required.

4. C0804 - If PID08 is present, then PID04 is required.

5. C0905 - If PID09 is present, then PID05 is required.

Semantics: 

1. Use PID03 to indicate the organization that publishes the code list being referred to.

2. PID04 should be used for industry-specific product description codes.

3. PID08 describes the physical characteristics of the product identified in PID04. A "Y" indicates that the specified attribute applies to this

item; an "N" indicates it does not apply. Any other value is indeterminate.

4. PID09 is used to identify the language being used in PID05.

Comments: 

1. If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are

used.

2. Use PID06 when necessary to refer to the product surface or layer being described in the segment.

3. PID07 specifies the individual code list of the agency specified in PID03.

DLMS Note:

Use this 2/PID/060 segment to tell the transaction set recipient to identify the DODAAC of the original shipping activity or to identify the

estimated ship date.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

PID01 349 Item Description Type

Description: Code indicating the format of

a description

M ID 1/1 Must use 1

Code Name

X Semi-structured (Code and Text)

PID05 352 Description

Description: A free-form description to

clarify the related data elements and their

content

DLMS Note: Use the following codes to

request the specified actions:

1 - Provide the DODAAC of the original

shipping activity

2 - Provide the improved Estimated

Shipping Date (ESD)

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

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

004010F869A3AA16 16 September 22, 2023

QTY Quantity Pos: 80 Max: 1

Detail - Optional

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

1. Must use in 2/HL/010 transaction loops to identify the applicable quantity.

2. Must use in all supply assistance requests.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

QTY01 673 Quantity Qualifier

Description: Code specifying the type of

quantity

M ID 2/2 Must use 1

Code Name

01 Discrete Quantity

DLMS Note:

1. Use to indicate the quantity requisitioned. Use to indicate the quantity shipped when requesting

shipment tracing

2. Use in requisition follow-ups, including requests for improved estimated delivery date, to indicate the

quantity requisitioned.

 3. Use in request for shipment tracing to indicate the quantity released to carrier.

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

1. Use to indicate the quantity requisitioned. Use to indicate the quantity shipped when requesting

shipment tracing

2. Use in requisition follow-ups, including requests for improved estimated delivery date, to indicate the

quantity requisitioned.

 3. Use in request for shipment tracing to indicate the quantity released to carrier.

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

AB Urgent Delivery Quantity

DLMS Note:

1. Use only in supply assistance request transactions to identify the quantity urgently required.

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

QTY02 380 Quantity

Description: Numeric value of quantity

DLMS Note: 1. Express as a whole

number with no decimal.

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

X R 1/15 Must use 1

QTY03 C001 Composite Unit of Measure

Description: To identify a composite unit of

measure(See Figures Appendix for

examples of use)

O Comp Used 1

QTY03-01 355 Unit or Basis for Measurement Code M ID 2/2 Must use 1
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F869A3AA16 17 September 22, 2023

Description: Code specifying the units in

which a value is being expressed, or

manner in which a measurement has been

taken

DLMS Note: 1. Use to identify the unit of

issue for the materiel.

2. DLMS users see the Unit of Issue and

Purchase Unit Conversion Table for

available codes.
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

004010F869A3AA16 18 September 22, 2023

REF Reference Identification Pos: 105 Max: 1

Detail - Optional

Loop: REF Elements: 4

User Option (Usage): Used

Purpose: To specify identifying information

Syntax Rules: 

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

Semantics: 

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

DLMS Note:

1. Use in all 2/HL/010 transaction loop iterations to identify the transaction number and suffix.

2. Use in all 2/HL/010 substitute item loop iterations to identify and describe acceptable substitute items.

3. Substitute item identification is a DLMS enhancement; see introductory DLMS note 2a.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

REF01 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

DLMS Note: 1. Use one of codes 1I, FQ,

S6, XA, XB or XD to identify acceptable

substitute materiel.

2. For requests for shipment tracing, use

the materiel identification provided in the

shipment status.

3. The following codes are authorized.

M ID 2/3 Must use 1

Code Name

1I Department of Defense Identification Code (DoDIC)

DLMS Note:

Use in 2/HL/010 substitute item loops only to identify acceptable substitute ammunition items.

86 Operation Number

DLMS Note:

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

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

9R Job Order Number

DLMS Note:

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

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

CO Customer Order Number

DLMS Note:

1. Use to identify the Customer Order Acceptance Record (COAR) applicable to the Job Order Number.

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

(or as applicable).

CU Clear Text Clause

DLMS Note:

Use in 2/HL/010 substitute item loops to identify a free-form description of acceptable substitute

nonstandard materiel when additional descriptive capability is required. Use with REF03 only.
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

Code Name

004010F869A3AA16 19 September 22, 2023

FQ Form Number

DLMS Note:

Use in 2/HL/010 substitute item loops to identify the form stock number. Enter the form stock number in

REF03. Refer to ADC 1287.

IT Internal Customer Number

DLMS Note:

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

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

IX Item Number

DLMS Note:

Use in 2/HL/010 substitute item loops to identify the applicable end item which applies to the

nonstandard materiel. Use REF04-02 to identify the National Stock Number (NSN) and use REF03 to

cite nomenclature.

S6 Stock Number

DLMS Note:

Use in 2/HL/010 substitute item loops to identify the publication stock number.

TG Transportation Control Number (TCN)

DLMS Note:

1. Use in transaction reference number loop to identify the shipment unit TCN.

2. May be used during legacy MILSTRIP/DLMS transition period when transaction contains a request

for identification of the initial transportation shipping activity. 

TN Transaction Reference Number

DLMS Note:

1. Must use in 2/HL/010 transaction loops to identify a transaction number assigned to the transaction. 

This is the document number.

2. When used with the requisition alert indicator (BSI09=83), this will be the requisition alert document

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

support agreement. Refer to ADC 381.

WP Warehouse Pick Ticket Number

DLMS Note:

1. Use to identify the picklist control number assigned to identify a specific job for which materiels are

being requisitioned and assembled together in support of planned maintenance. 

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

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

XA Substitute National Stock Number

DLMS Note:

Use in 2/HL/010 substitute item loops only to identify the acceptable substitute NSN.

XB Substitute Manufacturer's Part Number

DLMS Note:

Use in 2/HL/010 substitute item loops only to identify acceptable substitute nonstandard materiel.

XD Subsistence Identification Number

DLMS Note:

Use in 2/HL/010 substitute item loops to identify acceptable substitute subsistence materiel.

PWC Preliminary Work Candidate Number

DLMS Note:

1. Use to identify a Requisition Alert Document Number. 

2. Used by Navy Shipyards to associate the funded requisition Inquiry/Supply Assistance Request with

a previously submitted requisition alert. 

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

REF02 127 Reference Identification X AN 1/30 Used 1
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F869A3AA16 20 September 22, 2023

Description: Reference information as

defined for a particular Transaction Set or

as specified by the Reference Identification

Qualifier

REF03 352 Description

Description: A free-form description to

clarify the related data elements and their

content

DLMS Note: 1. Use as needed in

conjunction with code XB to identify the

nonstandard materiel nomenclature.

2. Use as needed in conjunction with code

CU to identify a free-form description of

acceptable nonstandard materiel.

3. Use as needed in conjunction with code

IX to identify the end item nomenclature.

4. Use with REF01 code FQ. Refer to ADC

1287.

X AN 1/80 Used 1

REF04 C040 Reference Identifier

Description: To identify one or more

reference numbers or identification

numbers as specified by the Reference

Qualifier

O Comp Used 1

REF04-01 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

DLMS Note: Use with REF01 code IX to

identify the NSN of the end-item associated

with the non-standard substitute item.

M ID 2/3 Must use 1

Code Name

NS National Stock Number

DLMS Note:

Use with REF01 code IX to identify the NSN of the end items associated with the non-standard

substitute item.

W7 Commercial and Government Entity (CAGE) Code

DLMS Note:

Use with REF01 code XB to uniquely identify a manufacturer's part number.

W8 Suffix

DLMS Note:

1. Use with REF01 code TN to identify a transaction number suffix when the original requisition has

been split.

2. When used with the Requisition Alert Indicator (BSI09=83), or when used in association with the

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

suffix. The Requisition Alert Document Number Suffix is an authorized DLMS enhancement under DLA

industrial activity support agreement. Refer to ADC 381.

1. Use with REF01 code TN to identify a transaction number suffix when the original requisition has

been split.

2. When used with the Requisition Alert Indicator (BSI09=83), or when used in association with the

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

suffix. The Requisition Alert Document Number Suffix is an authorized DLMS enhancement under DLA

industrial activity support agreement. Refer to ADC 381.

REF04-02 127 Reference Identification

Description: Reference information as

defined for a particular Transaction Set or

as specified by the Reference Identification

Qualifier

M AN 1/30 Must use 1

REF04-03 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

X ID 2/3 Used 1
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F869A3AA16 21 September 22, 2023

Code Name

MJ Model Number

DLMS Note:

Use with REF01 code XB to identify the manufacturer's model number of the nonstandard materiel.

REF04-04 127 Reference Identification

Description: Reference information as

defined for a particular Transaction Set or

as specified by the Reference Identification

Qualifier

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

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

004010F869A3AA16 22 September 22, 2023

N1 Name Pos: 110 Max: 1

Detail - Optional

Loop: N1 Elements: 5

User Option (Usage): Used

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

Syntax Rules: 

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

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

Comments: 

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

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

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

DLMS Note:

1. Must use this 2/N1/110 loop in the 2/HL/010 address loop to identify the organization originating and the organization to receive the

transaction set.

2. Use this 2/N1/110 loop in the individual 2/HL/010 transaction loops to identify an additional status recipient or the MCA. 

3. Use this 2/N1/110 loop in 2/HL/010 substitute item loops to identify the potential source of supply and end item manufacturer.

4. The substitute item loop is a DLMS enhancement for the supply assistance request transaction; see introductory DLMS note 2a.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N101 98 Entity Identifier Code

Description: Code identifying an

organizational entity, a physical location,

property or an individual

DLMS Note: The following codes are

authorized.

M ID 2/3 Must use 1

Code Name

BS Bill and Ship To

DLMS Note:

1. Use either this code, or both codes BT and ST, for reimbursable materiel. Use in requisition inquiry

to identify the organization which receives both the materiel and the billing for the materiel.

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

BT Bill-to-Party

DLMS Note:

1. Use with code ST for reimbursable materiel. Use in requisition inquiry to identify the organization to

receive the billing for the materiel when different from the organization receiving the materiel. Use

precludes the use of code BS.

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

CI Consignor

DLMS Note:

Use to identify the party to receive a request for shipment tracing. 

GP Gateway Provider

DLMS Note:

Use to identify the Defense Automatic Addressing System Center (DAASC).

OB Ordered By

DLMS Note:

Use to identify the requisitioning activity.
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

Code Name

004010F869A3AA16 23 September 22, 2023

PK Party to Receive Copy

DLMS Note:

Used between Navy and DLA for Navy requisitions submitted directly to other Component SoS, so that

DLA will be able to support follow-on actions on behalf of the Navy industrial activity (IA) under a DLA

industrial activity support agreement. Refer to ADC 377.

ST Ship To

DLMS Note:

1. Use with code BT for reimbursable materiel. Use in requisition inquiry to identify the organization to

receive the materiel, when different from the activity being billed for the materiel. Use precludes the use

of code BS.

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

XN Planning/Maintenance Organization

DLMS Note:

1. Used to identify a Shop Service Center/Shop Store.

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

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

Z1 Party to Receive Status

DLMS Note:

Use multiple iterations of the 2/N1/110 loop to identify additional status recipients when different from

Service/Agency prescribed status recipients.

Z3 Potential Source of Supply

DLMS Note:

Use in supply assistance requests as needed to identify potential alternative sources for the required

materiel.

Z5 Management Control Activity

DLMS Note:

Use for all Government Furnished Materiel (GFM) related transactions to identify the MCA associated

with the GFM transaction.

Z7 Mark-for Party

DLMS Note:

1. Use to identify an entity located within the ship-to address that is to actually receive the materiel.

2. The Mark-for Party may be identified by DoDAAC, RIC, clear text, or a combination of these. Only

one of DoDAAC or RIC may be used.

3. Maximum length of the mark for party is 24 positions: Mark-for clear text (with no DoDAAC or RIC)

displays on DoD shipment documents as two lines of 12 characters each. If text is combined with a

DoDAAC, up to 17 clear text characters will be allowed. If text is combined with a RIC, up to 20 clear

text characters will be allowed. A slash (/) will be inserted during printing of shipment documentation to

separate the DoDAAC or RIC from clear text; do not perpetuate the slash (/) in the DLMS transaction.

4. Authorized DLMS enhancement; see introductory DLMS note 2f. Refer to ADC 1009A.

5. Also use for Requisition Exception Data Transaction (DLA DIC YRZ-Transaction Code MF) to identify

mark-for delivery information. See introductory DLMS note 2e.

1. Use to identify an entity located within the ship-to address that is to actually receive the materiel.

2. The Mark-for Party may be identified by DoDAAC, RIC, clear text, or a combination of these. Only

one of DoDAAC or RIC may be used.

3. Maximum length of the mark for party is 24 positions: Mark-for clear text (with no DoDAAC or RIC)

displays on DoD shipment documents as two lines of 12 characters each. If text is combined with a

DoDAAC, up to 17 clear text characters will be allowed. If text is combined with a RIC, up to 20 clear

text characters will be allowed. A slash (/) will be inserted during printing of shipment documentation to

separate the DoDAAC or RIC from clear text; do not perpetuate the slash (/) in the DLMS transaction.

4. Authorized DLMS enhancement; see introductory DLMS note 2f. Refer to ADC 1009A.

5. Also use for Requisition Exception Data Transaction (DLA DIC YRZ-Transaction Code MF) to identify

mark-for delivery information. See introductory DLMS note 2e.

Z8 Last Known Source of Supply

DLMS Note:

Use to identify the supply source.

ZE End Item Manufacturer

DLMS Note:

Use in supply assistance requests to identify the manufacturer of the end item (Make). When using,

cite the actual name of the end item manufacturer in N102.

ZS Monitoring Party

DLMS Note:

Use to identify the International Logistics Control Office.
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

004010F869A3AA16 24 September 22, 2023

N102 93 Name

Description: Free-form name

DLMS Note: 1. Use with N101 Code ZE

for the end item manufacturer name. When

using N102 for this purpose, do not use

N103 and N104. DLMS enhancement; see

introductory DLMS note 2a.

DLMS Note: 1. Use with N101 Code ZE

for the end item manufacturer name. When

using N102 for this purpose, do not use

N103 and N104. DLMS enhancement; see

introductory DLMS note 2a.

2. Use with N101 Code Z7 to identify the

recipient of materiel. Total field length is

restricted to 24 clear text characters, when

not used in combination with a DoDAAC or

RIC. If combined with a Mark-for DoDAAC,

restrict clear text to 17 characters. If

combined with a Mark-for RIC, restrict clear

text to 20 characters. Authorized DLMS

enhancement; see introductory DLMS note

2f. Refer to ADC 1009A.

2. Use with N101 Code Z7 to identify the

recipient of materiel. Total field length is

restricted to 24 clear text characters, when

not used in combination with a DoDAAC or

RIC. If combined with a Mark-for DoDAAC,

restrict clear text to 17 characters. If

combined with a Mark-for RIC, restrict clear

text to 20 characters. Authorized DLMS

enhancement; see introductory DLMS note

2f. Refer to ADC 1009A.

X AN 1/60 Used 1

N103 66 Identification Code Qualifier

Description: Code designating the

system/method of code structure used for

Identification Code (67)

X ID 1/2 Used 1

Code Name

10 Department of Defense Activity Address Code (DODAAC)

33 Commercial and Government Entity (CAGE)

DLMS Note:

Use when the organization is a contractor not assigned a 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.

A2 Military Assistance Program Address Code (MAPAC)

DLMS Note:

Use to indicate the Security Assistance (SA) structured address data. Interpretation of this data may

require additional codes cited elsewhere in the transaction.

M4 Department of Defense Routing Identifier Code (RIC)

N104 67 Identification Code

Description: Code identifying a party or

other code

X AN 2/80 Used 1

N106 98 Entity Identifier Code

Description: Code identifying an

organizational entity, a physical location,

property or an individual

O ID 2/3 Used 1

Code Name

FR Message From

DLMS Note:

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

originating the transaction set.

2. For DLMS requests for shipment tracing resulting from conversion of the original MILSTRIP DIC

AFT, the originating activity will be identified as DAASC.

3. For DLMS follow-up requests for the DoDAAC of the initial transportation shipping activity resulting

from conversion of the original MILSTRIP DIC AFY, the originating activity will be identified as the

requisitioner due to lack of a from address in the MILS format.

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

originating the transaction set.

2. For DLMS requests for shipment tracing resulting from conversion of the original MILSTRIP DIC

AFT, the originating activity will be identified as DAASC.

3. For DLMS follow-up requests for the DoDAAC of the initial transportation shipping activity resulting

from conversion of the original MILSTRIP DIC AFY, the originating activity will be identified as the

requisitioner due to lack of a from address in the MILS format.

TO Message To
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

Code Name

004010F869A3AA16 25 September 22, 2023

DLMS Note:

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

receiving the transaction set.
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

004010F869A3AA16 26 September 22, 2023

PER Administrative Communications

Contact

Pos: 160 Max: 3

Detail - Optional

Loop: N1 Elements: 9

User Option (Usage): Used

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

Syntax Rules: 

1. P0304 - If either PER03 or PER04 is present, then the other is required.

2. P0506 - If either PER05 or PER06 is present, then the other is required.

3. P0708 - If either PER07 or PER08 is present, then the other is required.

DLMS Note:

1. Use only in supply assistance transactions.

2. Use in the 2/HL/010 organization loop with N106 code FR to identify a point of contact with the organization originating the transaction set.

3. Use in 2/HL/010 substitute item loops to identify a potential source of supply.

4. Use multiple repetitions to identify a point of contact (POC) and multiple communication numbers. When using multiple repetitions to

identify different communication numbers for a single POC, repeat the name cited in PER02.

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

1. Use only in supply assistance transactions.

2. Use in the 2/HL/010 organization loop with N106 code FR to identify a point of contact with the organization originating the transaction set.

3. Use in 2/HL/010 substitute item loops to identify a potential source of supply.

4. Use multiple repetitions to identify a point of contact (POC) and multiple communication numbers. When using multiple repetitions to

identify different communication numbers for a single POC, repeat the name cited in PER02.

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

PER01 366 Contact Function Code

Description: Code identifying the major

duty or responsibility of the person or group

named

DLMS Note: 1. Use code IC as needed, in

the 2/N1/110 Message From (FR) loop.

2. Use code SU in the 2/N1/110 Potential

Source of Supply (Z3) loop.

M ID 2/2 Must use 1

Code Name

IC Information Contact

DLMS Note:

Must use in the first repetition to identify the primary POC and communication number.

SU Supplier Contact

PER02 93 Name

Description: Free-form name

DLMS Note: Provide the last name, first

name, middle initial, and rate/rank/title, as

required, of the individual named as POC. 

Include blank spaces between name

components and periods after initials. Do

not include NMN or NMI when a middle

initial is not available.

DLMS Note: Provide the last name, first

name, middle initial, and rate/rank/title, as

required, of the individual named as POC. 

Include blank spaces between name

components and periods after initials. Do

not include NMN or NMI when a middle

initial is not available.

O AN 1/60 Must use 1

PER03 365 Communication Number Qualifier

Description: Code identifying the type of

communication number

DLMS Note: 1. Use to identify the

preferred method of communication in the

first repetition. Use PER05/6 and PER07/8

to identify additional communication

numbers. Use additional repetitions of the

DLMS Note: 1. Use to identify the

preferred method of communication in the

first repetition. Use PER05/6 and PER07/8

to identify additional communication

numbers. Use additional repetitions of the

X ID 2/2 Used 1
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F869A3AA16 27 September 22, 2023

PER segment to identify more than 3

numbers. 

2. Do not include blank spaces, dashes, or

parentheses between numbers.

Code Name

AU Defense Switched Network

DLMS Note:

Use to identify the DSN telephone number.

EM Electronic Mail

FX Facsimile

DLMS Note:

Use to identify the facsimile (FAX) telephone number.

IT International Telephone

DLMS Note:

Include country and city code.

TE Telephone

DLMS Note:

Use to identify the commercial telephone. Include the area code, number and extension, if applicable.

TL Telex

TX TWX

PER04 364 Communication Number

Description: Complete communications

number including country or area code

when applicable

X AN 1/80 Used 1

PER05 365 Communication Number Qualifier

Description: Code identifying the type of

communication number

DLMS Note: 1. Use to identify an alternate,

or secondary, communication number

which can be used to contact the specified

POC. 

2. Do not include blank spaces, dashes, or

parentheses between numbers.

X ID 2/2 Used 1

Code Name

AU Defense Switched Network

DLMS Note:

Use to identify the DSN telephone number.

EM Electronic Mail

EX Telephone Extension

DLMS Note:

Use immediately following code AU, IT, or TE to identify the telephone extension.

FX Facsimile

DLMS Note:

Use to identify the facsimile (FAX) telephone number.

IT International Telephone

DLMS Note:

Include country and city code.

TE Telephone

DLMS Note:

Use to identify the commercial telephone. Include the area code, number and extension, if applicable.

TL Telex
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

Code Name

004010F869A3AA16 28 September 22, 2023

TX TWX

PER06 364 Communication Number

Description: Complete communications

number including country or area code

when applicable

X AN 1/80 Used 1

PER07 365 Communication Number Qualifier

Description: Code identifying the type of

communication number

DLMS Note: 1. Use to identify an alternate,

or secondary, communication number

which can be used to contact the specified

POC. 

2. Do not include blank spaces, dashes, or

parentheses between numbers.

X ID 2/2 Used 1

Code Name

AU Defense Switched Network

DLMS Note:

Use to identify the DSN telephone number.

EM Electronic Mail

EX Telephone Extension

DLMS Note:

Use immediately following code AU, IT, or TE to identify the telephone extension.

FX Facsimile

DLMS Note:

Use to identify the facsimile (FAX) telephone number.

IT International Telephone

DLMS Note:

Include country and city code.

TE Telephone

DLMS Note:

Use to identify the commercial telephone. Include the area code, number and extension, if applicable.

TL Telex

TX TWX

PER08 364 Communication Number

Description: Complete communications

number including country or area code

when applicable

X AN 1/80 Used 1

PER09 443 Contact Inquiry Reference

Description: Additional reference number

or description to clarify a contact number

DLMS Note: Use only in the 2/HL/010

organization loop with N106 code FR to

indicate the office symbol or activity code

for the identified party.

O AN 1/20 Used 1
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

004010F869A3AA16 29 September 22, 2023

LM Code Source Information Pos: 170 Max: 1

Detail - Optional

Loop: LM Elements: 1

User Option (Usage): Used

Purpose: To transmit standard code list identification information

Comments: 

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

DLMS Note:

1. Use the 2/LM/170 loop in supply assistance transactions only in 2/HL/010 address loop to identify information related to the operational

necessity for obtaining the required materiel.

2. Must use the 2/LM/170 loop in 2/HL/010 transaction loops to identify DoD unique data.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LM01 559 Agency Qualifier Code

Description: Code identifying the agency

assigning the code values

M ID 2/2 Must use 1

Code Name

DF Department of Defense (DoD)
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

004010F869A3AA16 30 September 22, 2023

LQ Industry Code Pos: 180 Max: >1

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 in 2/HL/010 transaction

loops.

2. The following codes are authorized.

O ID 1/3 Must use 1

Code Name

0 Document Identification Code

DLMS Note:

1. The legacy MILSTRIP DIC is retained in the DLMS to facilitate transaction conversion in a mixed

legacy MILSTRIP/DLMS environment. Continued support of the DIC in a full DLMS environment will be

assessed at a future date. 

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

78 Project Code

DLMS Note:

Future streamlined data; see introductory DLMS note 2c.

79 Priority Designator Code

DLMS Note:

Future streamlined data; see introductory DLMS note 2c.

80 Advice Code

DLMS Note:

Future streamlined data; see introductory DLMS note 2c.

98 Reason for Requisitioning Code

DLMS Note:

1. Use to identify Reason for Requisitioning Code identifying the use of the materiel. 

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

A9 Supplemental Data

DLMS Note:

1. Use to identify supplemental address/data.

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

MILSTRIP Supplemented Address (SUPAAD) field. During this time, field size is restricted to 6

positions; see introductory DLMS note 2d.

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

see introductory DLMS note 2a.

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

1. Use to identify supplemental address/data.

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

MILSTRIP Supplemented Address (SUPAAD) field. During this time, field size is restricted to 6

positions; see introductory DLMS note 2d.

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

see introductory DLMS note 2a.

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 2c.
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

Code Name

004010F869A3AA16 31 September 22, 2023

AJ Utilization Code

DLMS Note:

1. Use to identify a specialized purpose for which the requisition is submitted.

2. Under legacy MILSTRIP, this is the first position of the document serial number within the document

number.

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

4. DLMS enhancement; see introductory DLMS note.

AK Distribution Code

AL Special Requirements Code

DLMS Note:

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

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

3. Use in conjunction with 2/LQ01/Code RC, Requirement Code, to complete the Air Force unique

NMCS/MICAP data requirement. 

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

DE Signal Code

DF Media and Status Code

GQ Group Qualifier Code

DLMS Note:

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

specific

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

Force-unique

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

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

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

23-110,

Volumes 1 and 2.

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

specific

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

Force-unique

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

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

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

23-110,

Volumes 1 and 2.

JN Mission Impact Statement Code

DLMS Note:

Use to identify the code value which best defines mission degradation created by the absence of the

required materiel.

KJ Assured Delivery Indicator

DLMS Note:

1. Use to identify, or modify, the Delivery Priority/Special Processing Code for materiel that has an

urgency of need within the maintenance shop and must be delivered within one hour of receipt of the

issue request. Value will be X (1 hour issue) when applicable.

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

3. A data maintenance action was approved in version 5030. The approved code/name is DPC –

Delivery Priority Code. DoD systems will continue to use Qualifier KJ to represent the Delivery

Priority/Special Processing Code until such time as a new ADC directs otherwise.

1. Use to identify, or modify, the Delivery Priority/Special Processing Code for materiel that has an

urgency of need within the maintenance shop and must be delivered within one hour of receipt of the

issue request. Value will be X (1 hour issue) when applicable.

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

3. A data maintenance action was approved in version 5030. The approved code/name is DPC –

Delivery Priority Code. DoD systems will continue to use Qualifier KJ to represent the Delivery

Priority/Special Processing Code until such time as a new ADC directs otherwise.

RC Requirement Code

DLMS Note:

1. Use to identify the Air Force Urgency Justification Code indicating the urgency of need and type of

requirement (justification) related to a Not Mission Capable Supply/Mission Impaired Capability Awaiting

Parts (NMCS/MICAP) condition.

2. Use in conjunction with Special Requirements Code N (2/LQ01/Code AL or perpetuated from legacy

MILSTRIP Required Delivery Date field). This is an Air Force unique data element, meaningful to the

Air Force only. Non-Air Force Components perpetuate without action. The code source is identified as

the Air Force Manual (AFMAN) 23-110, Volume 1 and 2.

A data maintenance action was approved in version 5010. The approved code/name is "UJC - Urgency 

1. Use to identify the Air Force Urgency Justification Code indicating the urgency of need and type of

requirement (justification) related to a Not Mission Capable Supply/Mission Impaired Capability Awaiting

Parts (NMCS/MICAP) condition.

2. Use in conjunction with Special Requirements Code N (2/LQ01/Code AL or perpetuated from legacy

MILSTRIP Required Delivery Date field). This is an Air Force unique data element, meaningful to the

Air Force only. Non-Air Force Components perpetuate without action. The code source is identified as

the Air Force Manual (AFMAN) 23-110, Volume 1 and 2.

A data maintenance action was approved in version 5010. The approved code/name is "UJC - Urgency 
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

Code Name

004010F869A3AA16 32 September 22, 2023

Justification Code".

COG Cognizance Symbol

DLMS Note:

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

EWR Evaluate Work Candidate Reason Lookup

DLMS Note:

1. Use to identify Requirement Churn Reason Code to identify materiel orders required by the industrial

site to complete planned work above what was originally identified during the pre-planned process

ordered and delivered after the start of the availability. 

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

IMC Item Management Code

DLMS Note:

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.

T05 Inspection Parameters

DLMS Note:

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

must be procured and inspected. 

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

LQ02 1271 Industry Code

Description: Code indicating a code from a

specific industry code list

X AN 1/30 Must use 1
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

004010F869A3AA16 33 September 22, 2023

FA1 Type of Financial Accounting Data Pos: 190 Max: 1

Detail - Optional

Loop: FA1 Elements: 2

User Option (Usage): Used

Purpose: To specify the organization controlling the content of the accounting citation, and the purpose associated with the accounting citation

Semantics: 

1. FA101 Identifies the organization controlling the assignment of financial accounting information.

2. FA102 Identifies the purpose of the accounting allowance or charge information.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

FA101 559 Agency Qualifier Code

Description: Code identifying the agency

assigning the code values

DLMS Note: This data element is required

for X12 syntax. Select the code that

corresponds to the organization that is

responsible for the assignment of the

DoDAAC used to construct the controlling

document number for the transaction.

DLMS Note: This data element is required

for X12 syntax. Select the code that

corresponds to the organization that is

responsible for the assignment of the

DoDAAC used to construct the controlling

document number for the transaction.

M ID 2/2 Must use 1

Code Name

DF Department of Defense (DoD)

DLMS Note:

Use to indicate that the Component is a Department of Defense agency, including Defense Logistics

Agency. Refer to ADC 1043.

DN Department of the Navy

DLMS Note:

Includes the United States Marine Corps.

DY Department of Air Force

DZ Department of Army

FG Federal Government

FA102 1300 Service, Promotion, Allowance, or

Charge Code

Description: Code identifying the service,

promotion, allowance, or charge

O ID 4/4 Must use 1

Code Name

A170 Adjustments

DLMS Note:

Use only for adjustments not specified by any other code.

A520 Base Charge

DLMS Note:

Use for materiel charges only.

C930 Export Shipping Charge

D340 Goods and Services Charge

DLMS Note:

Use for both materiel and related services.

F060 Other Accessorial Service Charge

F560 Premium Transportation

I260 Transportation Direct Billing

DLMS Note:

Use for non-premium transportation.
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

Code Name

004010F869A3AA16 34 September 22, 2023

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

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

004010F869A3AA16 35 September 22, 2023

FA2 Accounting Data Pos: 200 Max: >1

Detail - Mandatory

Loop: FA1 Elements: 2

User Option (Usage): Must use

Purpose: To specify the detailed accounting data

DLMS Note:

Use this 2/FA2/200 segment to identify the various components of the line of accounting.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

FA201 1196 Breakdown Structure Detail Code

Description: Codes identifying details

relating to a reporting breakdown structure

tree

M ID 2/2 Must use 1

Code Name

B5 Fund Code

I1 Abbreviated Department of Defense (DoD) Budget and Accounting Classification Code (BACC)

L1 Accounting Installation Number

DLMS Note:

Use to indicate the Authorization Accounting Authority (AAA)/Accounting and Disbursing Station

Number (ADSN)/Fiscal Station Number (FSN).

FA202 1195 Financial Information Code

Description: Code representing financial

accounting information

M AN 1/80 Must use 1
DLMS Implementation Convention (IC) 869A Requisition

Inquiry/Supply Assistance Request

ADC 50, 59, 76, 77, 88, 92, 94, 284, 284A, 304, 326, 377, 381, 388, 435, 1009A, 1043, 1043C,

1068, 1110, 1287, 1367, 1383, 1412 and 1454 DLM 4000.25

004010F869A3AA16 36 September 22, 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