DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

004010F870S4SA37 1 September 22, 2023

870 Order Status Report

Functional Group=RS

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

(870) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to report on the current

status of a requirement forecast, an entire purchase order, selected line items on a purchase order, selected products/services on a purchase

order, or purchase orders for a specific customer in their entirety or on a selection basis. The transaction set can also be used to report on the

current status of single or multiple requisitions. The report format allows for the inclusion of "reasons" relative to the status. This transaction set

may also be used to update the supplier's scheduled shipment or delivery dates. This transaction set can result from either an inquiry or a

prearranged schedule agreed to by the trading partners.

DLMS Note:

1. Organizations use this transaction set to report the current status of an entire order or a portion thereof. Use a single occurrence of this

transaction set to transmit single or multiple supply status transactions to one or more organizations.

a. DoD distinguishes among requisition status, notices of a direct vendor delivery, and responses to a supply assistance request.

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

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

3. This DLMS Implementation Convention (IC) contains:

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

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

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

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

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

4. This transaction may only be used to provide item unique identification (IUID) information in accordance with DLMS procedures for the

Unique Item Tracking (UIT) program for the Retail Transportation and Supply Receipt and Acknowledgement Interchange for Positive

Inventory Control (PIC) Nuclear Weapon Related Materiel (NWRM). Refer to the IUID web at URL: http://www.acq.osd.mil/dpap/pdi/uid/ for

DoD policy.

5. This revision to the DLMS IC incorporates the following Proposed DLMS Changes (PDC) and Approved DLMS Changes (ADC) listed.

PDC/ADCs are available from the DEDSO Web site:

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

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

- ADC 95, Revision to DS 870S, Supply Status, for UI

- ADC 191, Management Codes on Supply Status Transaction

- ADC 193, Administrative Revision to DLMS Supplements 4030 856S and 4010 870S

- ADC 221, Communication of Unit Price and Total Price under DLMS

- ADC 221A, Revised Procedures associated with the DLMS Enhancement for Communication of Unit Price

- ADC 229, Material Processing Center (MPC) Material Receipt and Delivery Supply Status

- ADC 274, DLMS and DLSS Changes to Support Army Exchange Pricing

- 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 279, Automated Downgrade for Priority Abuse and Reporting Procedures (Supply/MILSTRIP)

1. Organizations use this transaction set to report the current status of an entire order or a portion thereof. Use a single occurrence of this

transaction set to transmit single or multiple supply status transactions to one or more organizations.

a. DoD distinguishes among requisition status, notices of a direct vendor delivery, and responses to a supply assistance request.

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

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

3. This DLMS Implementation Convention (IC) contains:

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

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

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

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

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

4. This transaction may only be used to provide item unique identification (IUID) information in accordance with DLMS procedures for the

Unique Item Tracking (UIT) program for the Retail Transportation and Supply Receipt and Acknowledgement Interchange for Positive

Inventory Control (PIC) Nuclear Weapon Related Materiel (NWRM). Refer to the IUID web at URL: http://www.acq.osd.mil/dpap/pdi/uid/ for

DoD policy.

5. This revision to the DLMS IC incorporates the following Proposed DLMS Changes (PDC) and Approved DLMS Changes (ADC) listed.

PDC/ADCs are available from the DEDSO Web site:

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

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

- ADC 95, Revision to DS 870S, Supply Status, for UI

- ADC 191, Management Codes on Supply Status Transaction

- ADC 193, Administrative Revision to DLMS Supplements 4030 856S and 4010 870S

- ADC 221, Communication of Unit Price and Total Price under DLMS

- ADC 221A, Revised Procedures associated with the DLMS Enhancement for Communication of Unit Price

- ADC 229, Material Processing Center (MPC) Material Receipt and Delivery Supply Status

- ADC 274, DLMS and DLSS Changes to Support Army Exchange Pricing

- 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 279, Automated Downgrade for Priority Abuse and Reporting Procedures (Supply/MILSTRIP)
DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

004010F870S4SA37 2 September 22, 2023

- ADC 312, Denial Management Code in a Supply Status Transaction

- Administrative update completed on October 14, 2009 – 2/PO106/150 – Changed from “Used" to “Must use”.

- ADC 352, Request for Management Code for PQDR Replacement Requisitions

- ADC 375, New Management Code for Navy-Funded Non-Production Support Material Ordered under BRAC SS&D/IMSP

- ADC 379, New and Revised Supply Status Procedures to Support “Virtual Receipt” and Requisition Alert Processes under Navy BRAC

SS&D/IMSP

- 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 Material Release Order (MRO) Process

- ADC 407, Requirements for Unique Item Tracking (UIT) for positive Inventory Control (PIC) Nuclear Weapons related Material (NWRM) in

the DLMS Supply Status (870S) Supporting the Cargo Movement Operations System (CMOS) Interface

- ADC 436, Administrative Revisions to DLMS Supplements to Remove Obsolete Routing Identifier Code (RIC) “Streamline” Notes and

Update MILSTRIP/DLMS Documentation Associated with Routing Identifiers

- ADC 441, Exception Rules to Accommodate Communication of Ammunition/Ammunition Related Quantities in Excess of Five Digits

(Supply/MILSTRIP/MILSTRAP)

- ADC 441A (Addendum to ADC 441) Clarification to Exception Rules to Accommodate Communication of Ammunition/Ammunition Related

Quantities in Excess of Five Digits (Supply/MILSTRIP/MILSTRAP)

- ADC 448, Implementation of International Organization for Standardization (ISO) 3166-1 Codes for the Identification of Countries and their

Subdivisions

- ADC 448B, Delayed implementation for International Organization for Standardization (ISO) 3166-1 Codes for the Identification of

Countries and their Subdivisions

- ADC 455A, Revisions to Procedures and DLMS 870S, Supply Status, from DLA Disposition Services under Reutilization Business

Integration (RBI)

- ADC 465, Additional Contract-Related Data for 870S with BV Status

- ADC 466, Revised Procedures to Support Requisitioning and Transaction Exchange associated with DLA Disposition Services under

Reutilization Business Integration (RBI)

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

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

Purchase/Credit Card Payment

- ADC 1014, Revised Procedures for Inclusion of Contract Data in Transactions Associated with Government Furnished Property (GFP)

and Management Control Activity (MCA) Validation of Contractor Furnished Materiel (CFM) Requisitions

- ADC 1020, Inter-Service Ownership Transfer of Ammunition/ Ammunition Related Materiel

- ADC 1031, Foreign Military Sales (FMS) Repair Value

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

- ADC 1049, New Supply Status Code for Backorders Awaiting Engineering Support Activity (ESA) Support

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

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

- ADC 1161, Update uniform Procurement Instrument Identifier (PIID) numbering system in the Federal/DLMS Implementation Conventions

and DLMS Manuals (Supply/Contract Administration)

- ADC 1279, Material Processing Center (MPC) Transshipment Status

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

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

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

April 16, 2019

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

- ADC 1370, Administrative Update to Change Data Element N106 Usage from Must Use to Used

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

Office (DEDSO) - Completed on April 13, 2022

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

Indicator to Wide Area Workflow

- ADC 1420, Other Transaction (OT) Agreements Instrument Type and Procurement Instrument Identifier (PIID) Construct (Supply/Contract

Administration)

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

- ADC 312, Denial Management Code in a Supply Status Transaction

- Administrative update completed on October 14, 2009 – 2/PO106/150 – Changed from “Used" to “Must use”.

- ADC 352, Request for Management Code for PQDR Replacement Requisitions

- ADC 375, New Management Code for Navy-Funded Non-Production Support Material Ordered under BRAC SS&D/IMSP

- ADC 379, New and Revised Supply Status Procedures to Support “Virtual Receipt” and Requisition Alert Processes under Navy BRAC

SS&D/IMSP

- 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 Material Release Order (MRO) Process

- ADC 407, Requirements for Unique Item Tracking (UIT) for positive Inventory Control (PIC) Nuclear Weapons related Material (NWRM) in

the DLMS Supply Status (870S) Supporting the Cargo Movement Operations System (CMOS) Interface

- ADC 436, Administrative Revisions to DLMS Supplements to Remove Obsolete Routing Identifier Code (RIC) “Streamline” Notes and

Update MILSTRIP/DLMS Documentation Associated with Routing Identifiers

- ADC 441, Exception Rules to Accommodate Communication of Ammunition/Ammunition Related Quantities in Excess of Five Digits

(Supply/MILSTRIP/MILSTRAP)

- ADC 441A (Addendum to ADC 441) Clarification to Exception Rules to Accommodate Communication of Ammunition/Ammunition Related

Quantities in Excess of Five Digits (Supply/MILSTRIP/MILSTRAP)

- ADC 448, Implementation of International Organization for Standardization (ISO) 3166-1 Codes for the Identification of Countries and their

Subdivisions

- ADC 448B, Delayed implementation for International Organization for Standardization (ISO) 3166-1 Codes for the Identification of

Countries and their Subdivisions

- ADC 455A, Revisions to Procedures and DLMS 870S, Supply Status, from DLA Disposition Services under Reutilization Business

Integration (RBI)

- ADC 465, Additional Contract-Related Data for 870S with BV Status

- ADC 466, Revised Procedures to Support Requisitioning and Transaction Exchange associated with DLA Disposition Services under

Reutilization Business Integration (RBI)

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

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

Purchase/Credit Card Payment

- ADC 1014, Revised Procedures for Inclusion of Contract Data in Transactions Associated with Government Furnished Property (GFP)

and Management Control Activity (MCA) Validation of Contractor Furnished Materiel (CFM) Requisitions

- ADC 1020, Inter-Service Ownership Transfer of Ammunition/ Ammunition Related Materiel

- ADC 1031, Foreign Military Sales (FMS) Repair Value

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

- ADC 1049, New Supply Status Code for Backorders Awaiting Engineering Support Activity (ESA) Support

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

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

- ADC 1161, Update uniform Procurement Instrument Identifier (PIID) numbering system in the Federal/DLMS Implementation Conventions

and DLMS Manuals (Supply/Contract Administration)

- ADC 1279, Material Processing Center (MPC) Transshipment Status

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

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

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

April 16, 2019

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

- ADC 1370, Administrative Update to Change Data Element N106 Usage from Must Use to Used

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

Office (DEDSO) - Completed on April 13, 2022

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

Indicator to Wide Area Workflow

- ADC 1420, Other Transaction (OT) Agreements Instrument Type and Procurement Instrument Identifier (PIID) Construct (Supply/Contract

Administration)

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

Heading:

Pos Id Segment Name Req Max Use Repeat Notes Usage

10 ST Transaction Set Header M 1 Must use

20 BSR Beginning Segment for Order

Status Report

M 1 Must use

* 42 TD3 Carrier Details (Equipment) O 1 Not Used

* 43 TD4 Carrier Details (Special Handling, O 1 Not Used
DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

Pos Id Segment Name Req Max Use Repeat Notes Usage

004010F870S4SA37 3 September 22, 2023

or Hazardous Materials, or Both) * 44 TD5 Carrier Details (Routing

Sequence/Transit Time)

O 1 Not Used

* 45 DTM Date/Time Reference O 10 Not Used

* LOOP ID - REF * LOOP ID - REF >1

* 46 REF Reference Identification O 1 Not Used

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

LOOP ID - N1 LOOP ID - N1 200

50 N1 Name O 1 Used

* 60 N2 Additional Name Information O 2 Not Used

* 70 N3 Address Information O 2 Not Used

* 80 N4 Geographic Location O 1 Not Used

* 90 REF Reference Identification O 12 Not Used

* 100 PER Administrative Communications

Contact

O 3 Not Used

* 105 PWK Paperwork O 1 Not Used

* LOOP ID - LM * LOOP ID - LM 10

* 120 LM Code Source Information O 1 Not Used

130 LQ Industry Code M 100 Must use

Detail:

Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - HL LOOP ID - HL 1000

10 HL Hierarchical Level M 1 Must use

* 20 PRF Purchase Order Reference O 1 Not Used

* LOOP ID - ISR * LOOP ID - ISR 104

* 30 ISR Item Status Report O 1 Not Used

* 40 PID Product/Item Description O 6 Not Used

* 50 QTY Quantity O 4 Not Used

* 70 PER Administrative Communications

Contact

O 3 Not Used

80 DTM Date/Time Reference O 10 Used

86 CS Contract Summary O 3 N2/86 Used

LOOP ID - REF LOOP ID - REF >1

87 REF Reference Identification O 1 Used

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

LOOP ID - N1 LOOP ID - N1 200

90 N1 Name O 1 Used

* 100 N2 Additional Name Information O 2 Not Used

* 110 N3 Address Information O 2 Not Used

* 120 N4 Geographic Location O 1 Not Used

* 130 REF Reference Identification O 12 Not Used

* 140 PER Administrative Communications

Contact

O 3 Not Used

LOOP ID - LM LOOP ID - LM 10

144 LM Code Source Information O 1 Used

145 LQ Industry Code M 100 Must use

LOOP ID - PO1 LOOP ID - PO1 1000

150 PO1 Baseline Item Data O 1 Must use

* 155 CUR Currency O 1 Not Used

* 160 SLN Subline Item Detail O 100 Not Used
DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

Pos Id Segment Name Req Max Use Repeat Notes Usage

004010F870S4SA37 4 September 22, 2023

* 170 PO3 Additional Item Detail O 1 Not Used

* 180 PID Product/Item Description O 1000 Not Used

* 190 MEA Measurements O 40 Not Used

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

LOOP ID - ISR LOOP ID - ISR 104

210 ISR Item Status Report O 1 Must use

* 220 PID Product/Item Description O 6 Not Used

230 QTY Quantity O 4 Used

240 DTM Date/Time Reference O 10 Used

* 250 N1 Name O 1 Not Used

* 251 N2 Additional Name Information O 2 Not Used

* 252 N3 Address Information O 2 Not Used

* 253 N4 Geographic Location O 1 Not Used

* 260 TD1 Carrier Details (Quantity and

Weight)

O 1 Not Used

* 270 TD5 Carrier Details (Routing

Sequence/Transit Time)

O 1 Not Used

* 280 TD3 Carrier Details (Equipment) O 1 Not Used

* 290 TD4 Carrier Details (Special Handling,

or Hazardous Materials, or Both)

O 1 Not Used

300 REF Reference Identification O 12 Used

* 310 SAC Service, Promotion, Allowance,

or Charge Information

O 25 Not Used

LOOP ID - LM LOOP ID - LM 10

320 LM Code Source Information O 1 Used

330 LQ Industry Code M 100 Must use

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

340 LX Assigned Number O 1 N2/340 Used

350 REF Reference Identification O >1 Used

* 360 N1 Name O 1 Not Used

* 370 DTM Date/Time Reference O 10 Not Used

* LOOP ID - LM * LOOP ID - LM 10

* 380 LM Code Source Information O 1 Not Used

390 LQ Industry Code M 100 Must use

Summary:

Pos Id Segment Name Req Max Use Repeat Notes Usage

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

20 SE Transaction Set Trailer M 1 Must use

Notes: 

2/86 Use is limited to intra-organizational transactions.

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

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

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

value of quantities ordered (PO102) for each PO1 segment.
DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

004010F870S4SA37 5 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

870 Order Status Report

ST02 329 Transaction Set Control Number

Description: Identifying control number

that must be unique within the transaction

set functional group assigned by the

originator for a transaction set

DLMS Note: A unique number assigned by

the originator of the transaction set, or the

originator's application program.

M AN 4/9 Must use 1
DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

004010F870S4SA37 6 September 22, 2023

BSR Beginning Segment for Order Status

Report

Pos: 20 Max: 1

Heading - Mandatory

Loop: N/A Elements: 6

User Option (Usage): Must use

Purpose: To indicate the beginning of an Order Status Report Transaction Set

Semantics: 

1. BSR03 indicates a status report document number assigned by the sender.

2. BSR04 indicates the date of this report from the sender.

3. BSR07 indicates the time of this report from the sender.

4. BSR08 indicates a status report document number assigned by the inquirer.

5. BSR09 indicates the date this report was requested from the sender by the inquirer.

6. BSR10 indicates the time this report was requested from the sender by the inquirer.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

BSR01 850 Status Report Code

Description: Code indicating the reason

for sending the report

M ID 1/2 Must use 1

Code Name

4 Response to Requisition

DLMS Note:

1. Use to indicate requisition supply status.

2. Also used to provide detailed contract information in combination with Supply Status BV (combined

MILSTRIP DIC AE_ and AB_). (Refer to ADC 465.)

5 Notice of Response to Direct Vendor Delivery

DLMS Note:

Use to indicate that the supply source is providing the required materiel directly from a commercial

source. Use when direct vendor delivery notice is provided as a separate transaction (MILSTRIP DIC

AB_) pending transition to enhanced BV Status under ADC 465.

6 Notice of Response to Supply Assistance

DLMS Note:

Use to indicate the response to a supply assistance inquiry.

BSR02 847 Order/Item Code

Description: Code identifying a group of

orders and items

M ID 1/2 Must use 1

Code Name

CO All Orders - Unshipped Items

DLMS Note:

Use to indicate that all orders remain open.

BSR03 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

BSR04 373 Date M DT 8/8 Must use 1
DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F870S4SA37 7 September 22, 2023

Description: Date expressed as

CCYYMMDD

DLMS Note: This date corresponds to the

Universal Time Coordinate (UTC).

BSR07 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 in UTC.

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

format.

O TM 4/8 Must use 1

BSR11 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 supply status 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. 
DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

004010F870S4SA37 8 September 22, 2023

N1 Name Pos: 50 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:

1. Must use this N1 loop to identify the organization originating the transaction set.

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N101 98 Entity Identifier Code

Description: Code identifying an

organizational entity, a physical location,

property or an individual

DLMS Note: 1. Use only one of codes GP,

Z4, Z5 or ZS.

2. The following codes are authorized.

M ID 2/3 Must use 1

Code Name

1Q Military Facility

DLMS Note:

For intra-AF supply status for lateral movements, to identify the activity shipping the materiel and

providing supply status.

GP Gateway Provider

DLMS Note:

Use to indicate DLA Transaction Services is providing rerouting of status.

SB Storage Area

DLMS Note:

1. Use to identify the distribution center generating the supply status.

 2. Used when providing Materiel Processing Center (MPC) status.

3. Use to identify the storage activity when the storage activity is the originator of the transaction

implemented. This is applicable as a DLMS enhancement to allow specific separate identification of

owner/manager and storage activity RIC for ammunition and ammunition related transactions. Refer to

Approved Addendum to ADC 441A.

1. Use to identify the distribution center generating the supply status.

 2. Used when providing Materiel Processing Center (MPC) status.

3. Use to identify the storage activity when the storage activity is the originator of the transaction

implemented. This is applicable as a DLMS enhancement to allow specific separate identification of

owner/manager and storage activity RIC for ammunition and ammunition related transactions. Refer to

Approved Addendum to ADC 441A.

Z4 Owning Inventory Control Point

DLMS Note:

Use to indicate the source of supply furnishing status.

Z5 Management Control Activity

DLMS Note:

Use to identify the MCA furnishing the status.

ZS Monitoring Party
DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

Code Name

004010F870S4SA37 9 September 22, 2023

DLMS Note:

Use to identify the International Logistics Control Office furnishing the status.

N103 66 Identification Code Qualifier

Description: Code designating the

system/method of code structure used for

Identification Code (67)

X ID 1/2 Must use 1

Code Name

10 Department of Defense Activity Address Code (DODAAC)

M4 Department of Defense Routing Identifier Code (RIC)

N104 67 Identification Code

Description: Code identifying a party or

other code

X AN 2/80 Must use 1

N106 98 Entity Identifier Code

Description: Code identifying an

organizational entity, a physical location,

property or an individual

O ID 2/3 Used 1

Code Name

FR Message From

DLMS Note:

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

the transaction set.
DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

004010F870S4SA37 10 September 22, 2023

HL Hierarchical Level Pos: 10 Max: 1

Detail - Mandatory

Loop: HL Elements: 2

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:

The transaction set hierarchical data structure is transaction number only.

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 numeric 1. In each

subsequent loop iteration, increase

incrementally by 1.

M AN 1/12 Must use 1

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

W Transaction Reference Number

DLMS Note:

Use to identify the individual transaction supply status loops.
DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

004010F870S4SA37 11 September 22, 2023

DTM Date/Time Reference Pos: 80 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 to indicate the transaction preparation date.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

DTM01 374 Date/Time Qualifier

Description: Code specifying type of date

or time, or both date and time

M ID 3/3 Must use 1

Code Name

097 Transaction Creation

DLMS Note:

Use to indicate the date of transaction preparation.

DTM02 373 Date

Description: Date expressed as

CCYYMMDD

X DT 8/8 Must use 1
DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

004010F870S4SA37 12 September 22, 2023

CS Contract Summary Pos: 86 Max: 3

Detail - Optional

Loop: HL Elements: 14

User Option (Usage): Used

Purpose: To provide information about a contract

Syntax Rules: 

1. P0405 - If either CS04 or CS05 is present, then the other is required.

Semantics: 

1. CS09 is the permissible overage as a percentage of the total contract line item number (CLIN) quantity.

2. CS10 is the permissible shortage as a percentage of the total contract line item number (CLIN) quantity.

3. CS11 is the permissible overage dollar value specified by the contract above which discrepancy action is taken.

4. CS14 is the Unit of Measure stipulated in the contract.

5. CS15 is the contract line item number (CLIN) unit price specified in the contract.

6. CS17 conveys the Critical Application Indicator. A "Y" indicates that a Critical Application Indicator is specified in the contract; an "N"

indicates that no Critical Application Indicator is specified in the contract.

7. CS18 conveys the Special Requirements Indicator. A "Y" indicates that a Special Requirements Indicator (requiring special testing and

or evaluation) is specified in the contract; an "N" indicates that no Special Requirements Indicator is specified in the contract.

Comments: 

1. CS04 may be used to identify the Contract Line Item Number (CLIN) or Extended (or Exhibit) Line Item Number (ELIN).

2. CS07 and CS13 can be used to indicate two different types of special services required.

DLMS Note:

Use in direct vendor delivery transactions to identify basic contract information related to the acquisition action.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

CS01 367 Contract Number

Description: Contract number

DLMS Note: Use to identify the

procurement instrument identifier (PIID).

Use the legacy procurement instrument

identification number (PIIN) pending

transition to the PIID. When procurement is

authorized under a PIID call/order number

(F or M in 9th position), provide the value in

the PIID field. For Other Transaction (OT)

agreements, the type of instrument (9th

position of PIID) will be a 3 for Research

OTs or 9 for Prototype and Production OTs.

Refer to ADC 1161A or ADC 1420.

DLMS Note: Use to identify the

procurement instrument identifier (PIID).

Use the legacy procurement instrument

identification number (PIIN) pending

transition to the PIID. When procurement is

authorized under a PIID call/order number

(F or M in 9th position), provide the value in

the PIID field. For Other Transaction (OT)

agreements, the type of instrument (9th

position of PIID) will be a 3 for Research

OTs or 9 for Prototype and Production OTs.

Refer to ADC 1161A or ADC 1420.

O AN 1/30 Must use 1

CS02 327 Change Order Sequence Number

Description: Number assigned by the

orderer identifying a specific change or

revision to a previously transmitted

transaction set

DLMS Note: Use to identify a modification

number to the cited contract.

O AN 1/8 Used 1

CS03 328 Release Number

Description: Number identifying a release

against a Purchase Order previously placed

by the parties involved in the transaction

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

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F870S4SA37 13 September 22, 2023

DLMS Note: 1. Use to identify the legacy

four-position call/order number associated

with the PIIN.

2. Do not use for the PIID call/order

number. The PIID call/order number is

mapped to CS01. Refer to ADC 1161A.

CS04 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

DLMS Note: Use the appropriate code,

based on the CS01 information, when the

Exhibit Line Item Number (ELIN) or

Contract Line Item Number (CLIN) are

known.

DLMS Note: Use the appropriate code,

based on the CS01 information, when the

Exhibit Line Item Number (ELIN) or

Contract Line Item Number (CLIN) are

known.

X ID 2/3 Used 1

Code Name

83 Extended (or Exhibit) Line Item Number (ELIN)

DLMS Note:

Use to identify the ELIN, or the ELIN including the Sub Exhibit Line Item Number (SUBELIN), as

appropriate.

C7 Contract Line Item Number

DLMS Note:

Use to identify the CLIN, or the CLIN including the Sub Contract Line Item Number (SUBCLIN), as

appropriate.

CS05 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

CS07 560 Special Services Code

Description: Code identifying the special

service

DLMS Note: 1. Use to identify the contract

specification for materiel acceptance.

2. Use with Supply Status BV to identify the

acceptance point. (Refer to ADC 465)

O ID 2/10 Used 1

Code Name

AD Accept at Destination

AO Accept at Origin

ZZ Mutually Defined

DLMS Note:

Use ZZ to indicate Acceptance by Other when destination acceptance shall be performed by an activity

other than the ship-to activity.

CS09 954 Percent

Description: Percentage expressed as a

decimal

DLMS Note: Use with Supply Status BV to

identify the allowable overage by percent. 

(Refer to ADC 465)

O R 1/10 Used 1

CS10 954 Percent

Description: Percentage expressed as a

decimal

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

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F870S4SA37 14 September 22, 2023

DLMS Note: Use with Supply Status BV to

identify the allowable shortage by percent. 

(Refer to ADC 465)

CS11 782 Monetary Amount

Description: Monetary amount

DLMS Note: 1. Use the dollar amount from

the excess quantity clause. Express as a

whole number with no decimal.

2. Use with Supply Status BV to identify the

allowable dollar amount specified in the

excess quantity clause when applicable. 

(Refer to ADC 465)

O R 1/18 Used 1

CS13 560 Special Services Code

Description: Code identifying the special

service

DLMS Note: 1. Use to identify the contract

specification for materiel inspection.

2. Use with Supply Status BV to identify

when contract terms specify inspection

requirements. (Refer to ADC 465)

O ID 2/10 Used 1

Code Name

IM Inspect at Destination

DLMS Note:

Use Code IM to indicate Inspection Performed at Destination when origin inspection does not apply

and inspection requirements shall be satisfied by the ship-to activity.

IO Inspect at Origin

G0052 Government Inspection

DLMS Note:

Use code G0052 to indicate Inspection Performed by Other when origin inspection does not apply and

inspection requirements shall be satisfied by an activity other than the ship-to activity.

CS14 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 identify the

purchase unit of issue, if different from the

standard unit of issue. 

2. Use with Supply Status BV to identify the

purchase unit if different from the unit of

issue. (Refer to ADC 465)

3. DLMS users see the Unit of Issue and

Purchase Unit Conversion Table for

available codes.

O ID 2/2 Used 1

CS15 212 Unit Price

Description: Price per unit of product,

service, commodity, etc.

DLMS Note: Use to identify the CLIN unit

price when CS11 contains a value.

O R 1/17 Used 1

CS17 1073 Yes/No Condition or Response Code

Description: Code indicating a Yes or No

condition or response

O ID 1/1 Used 1
DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F870S4SA37 15 September 22, 2023

DLMS Note: Use with Supply Status BV to

identify when the contract specifies a

Certificate of Conformance (CoC) is

applicable. (Refer to ADC 465)

Code Name

N No

Y Yes

CS18 1073 Yes/No Condition or Response Code

Description: Code indicating a Yes or No

condition or response

DLMS Note: Use with Supply Status BV to

identify when the contract specifies a

Certificate of Quality Conformance (CoQC)

is applicable. (Refer to ADC 465)

O ID 1/1 Used 1

Code Name

N No

Y Yes
DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

004010F870S4SA37 16 September 22, 2023

REF Reference Identification Pos: 87 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. To provide financial data: cite the fund purpose code and either or both of the fund code and the long-line accounting data. When citing

long-line accounting data use REF03 and components of REF04. 

2. Use multiple repetitions to identify the customer assigned transaction number, Government Furnished Materiel (GFM) related information,

and funding data.

3. DLMS users see the Accounting Classification Appendix for specific entries for the basic appropriation number and supplemental

accounting classification data.

1. To provide financial data: cite the fund purpose code and either or both of the fund code and the long-line accounting data. When citing

long-line accounting data use REF03 and components of REF04. 

2. Use multiple repetitions to identify the customer assigned transaction number, Government Furnished Materiel (GFM) related information,

and funding data.

3. DLMS users see the Accounting Classification Appendix for specific entries for the basic appropriation number and supplemental

accounting classification data.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

REF01 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

DLMS Note: The following codes are

authorized.

M ID 2/3 Must use 1

Code Name

86 Operation Number

DLMS Note:

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

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

9R Job Order Number

DLMS Note:

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

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

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

FG Fund Identification Number

DLMS Note:

Use to identify the fund purpose code. Cite any fund purpose code in REF02 except CR or DR.

TN Transaction Reference Number

DLMS Note:

1. Must use to identify the customer assigned transaction number.

2. This is the document number.
DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

Code Name

004010F870S4SA37 17 September 22, 2023

3. When status is applicable to a requisition alert, this field will perpetuate the alert document number. 

The requisition alert is an Authorized DLMS enhancement under DLA industrial activity support

agreement. Refer to ADC 381.

WO Work Order Number

DLMS Note:

1. Use to identify a maintenance work order number.

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

BDG Badge Number

DLMS Note:

1. Use with local industrial activity worksite delivery status to provide the badge number of the artisan

to whom the materiel was delivered. Refer to ADC 379

2. This is an X12 Migration Code approved for use in Version 4030. Implementers must manual update

4010 software to recognize this code.

PWC Preliminary Work Candidate Number

DLMS Note:

1. Use to identify a Requisition Alert Document Number. 

2. Used in support of Navy Shipyards to associate the funded requisition with a previously submitted

requisition alert. 

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

REF02 127 Reference Identification

Description: Reference information as

defined for a particular Transaction Set or

as specified by the Reference Identification

Qualifier

X AN 1/30 Must use 1

REF03 352 Description

Description: A free-form description to

clarify the related data elements and their

content

DLMS Note: Use only with REF01 code FG

and REF04 code AT to cite the

supplemental accounting classification data.

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

DLMS Note: When providing financial data

(REF01 code FG):

If providing only the fund code use

REF04-01 code FU and cite the fund code

in REF04-02.

If providing the long-line accounting data

use REF04-01 code AT and cite the basic

appropriation data in REF04-02. Use

REF04-03 code 10 and cite the accounting

station number in REF04-04.

If providing both use REF04-01 code FU,

REF04-03 code AT and REF04-05 code 10

citing the related data in the following data

element of the pair.

Syntax: 

1. P0304 - If either C04003 or C04004 is

present, then the other is required.

O Comp Used 1
DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F870S4SA37 18 September 22, 2023

2. P0506 - If either C04005 or C04006 is

present, then the other is required.

REF04-01 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

M ID 2/3 Must use 1

Code Name

10 Account Managers Code

DLMS Note:

Use in one of REF04-03 or REF04-05 to identify the authorized accounting activity (AAA)/accounting

disbursing station number (ADSN)/fiscal station number (FSN).

AT Appropriation Number

DLMS Note:

Use in one of REF04-01 or REF04-03 to identify the basic appropriation data.

FU Fund Code

DLMS Note:

Use with REF01 code FG to identify the fund code.

W1 Disposal Turn-In Document Number

DLMS Note:

1. Use in conjunction with the controlling document number for the transaction cited in REF01 Code TN.

 2. Use for DLA Disposition Services requisition supply status to identify the specific DTID number

shipped under the controlling document number/suffix code. Authorized DLMS enhancement. Refer to

ADC 455A.

W8 Suffix

DLMS Note:

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

will be the requisition alert document suffix. 

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

Code Name

60 Account Suffix Code

DLMS Note:

Use in conjunction with the DTID Number (REF04 Qualifier W1) to identify the DTID Suffix Code, when

applicable. DLMS enhancement, see ADC 466.

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

REF04-05 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

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

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F870S4SA37 19 September 22, 2023

REF04-06 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)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

004010F870S4SA37 20 September 22, 2023

N1 Name Pos: 90 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/090 loop to identify the organization to receive the transaction.

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N101 98 Entity Identifier Code

Description: Code identifying an

organizational entity, a physical location,

property or an individual

DLMS Note: The following codes are

authorized.

M ID 2/3 Must use 1

Code Name

C4 Contract Administration Office

DLMS Note:

Use with Supply Status BV for direct vendor deliveries to identify the Contract Administration Office

(CAO). (Refer to ADC 465)

GP Gateway Provider

DLMS Note:

Use to identify DLA Transaction Services as the “TO” organization for Component-generated supply

status forwarded for DAAS distribution to status recipients under MILSTRIP/DLMS distribution rules

(DLMS equivalent of AE8).

KK Registering Party

DLMS Note:

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

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

Must be used with 2/N106/90 code ‘PK-Party to Receive Copy’ to identify that this is only an information

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

in 2/N104.

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

use in conjunction with 2/N106 code PK and cite the applicable Routing Identifier in 2/N104.

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

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

Must be used with 2/N106/90 code ‘PK-Party to Receive Copy’ to identify that this is only an information

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

in 2/N104.

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

use in conjunction with 2/N106 code PK and cite the applicable Routing Identifier in 2/N104.

PR Payer

DLMS Note:

Use for direct vendor deliveries to identify the paying office for the related acquisition action.

SB Storage Area

DLMS Note:

1. Use to identify the storage activity applicable to the status provided.
DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

Code Name

004010F870S4SA37 21 September 22, 2023

2. When implemented as a DLMS enhancement to allow specific separate identification of Owning

Inventory Control Point and Storage Activity RIC for and ammunition related transactions, the storage

activity may be the actual initiator of the status on behalf of the ICP identified at 1/N101/50 Code Z4

(N106=FR). Refer to ADC 441.

SH Shipper

DLMS Note:

Use for direct vendor deliveries to identify the organization that will initiate the materiel shipment for the

related acquisition action.

SU Supplier/Manufacturer

DLMS Note:

Use with Supply Status BV for direct vendor deliveries to identify the contractor providing the materiel

for the related acquisition order. (Refer to ADC 465)

UQ Subsequent Owner

DLMS Note:

Use only on supply status subsequent to a referral order to initiate an inter-Service ammunition or

ammunition-related ownership transfer with no physical movement of materiel. Use to identify the RIC

to which ownership is being transferred (the New Owner RIC). DLMS enhancement. Refer to ADC

1020.

WD Storage Facility at Destination

DLMS Note:

1. Use to identify the Material Processing Center (MPC).

2. When used with Status Code NY, this will identify the MPC to which materiel is transshipped. 

Identify the shipping MPC as the transaction originator. Refer to ADC 1279.

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:

Must use to identify the organization to receive supply status. Use multiple iterations to identify all

status recipients.

Z4 Owning Inventory Control Point

DLMS Note:

Use to identify the owner/manager when implemented as a DLMS enhancement to allow specific

separate identification of owner/manager and storage activity RIC for ammunition and ammunition

related transactions. Refer to Approved Addendum to ADC 441A.

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. Authorized DLMS enhancement; see introductory DLMS note 3f. Refer to ADC 1009A.

Z8 Last Known Source of Supply

DLMS Note:

1. Use for requisition supply status transactions to identify the supply source to which any future

inquires should be addressed.

2. For intra-AF supply status for lateral movements, may be used to identify the shipping activity to

which any future inquires should be addressed. Refer to ADC 407.

N102 93 Name

Description: Free-form name

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

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F870S4SA37 22 September 22, 2023

DLMS Note: Use with N101 Code Z7 to

identify the recipient of materiel. Total field

length is restricted to 24 characters. 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

3f. Refer to ADC 1009A.

DLMS Note: Use with N101 Code Z7 to

identify the recipient of materiel. Total field

length is restricted to 24 characters. 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

3f. Refer to ADC 1009A.

N103 66 Identification Code Qualifier

Description: Code designating the

system/method of code structure used for

Identification Code (67)

X ID 1/2 Must use 1

Code Name

10 Department of Defense Activity Address Code (DODAAC)

33 Commercial and Government Entity (CAGE)

DLMS Note:

Use with Supply Status BV for direct vendor delivery 2/N1/090 supplier (Code SU) to identify the

contractor providing the materiel.

92 Assigned by Buyer or Buyer's Agent

DLMS Note:

Use with N101 Entity Identifier 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)

M4 Department of Defense Routing Identifier Code (RIC)

N104 67 Identification Code

Description: Code identifying a party or

other code

X AN 2/80 Must use 1

N106 98 Entity Identifier Code

Description: Code identifying an

organizational entity, a physical location,

property or an individual

O ID 2/3 Used 1

Code Name

PK Party to Receive Copy

DLMS Note:

1. Use when appropriate to send an information copy to a Component UIT registry. For use with N101

code ‘KK’.

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

use in conjunction with 2/N101 code ‘KK’ and cite the applicable Routing Identifier in 2/N104.

3. Except as noted above, DLMS enhancement; Refer to ADC 407.

TO Message To

DLMS Note:

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

transaction.
DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

004010F870S4SA37 23 September 22, 2023

LM Code Source Information Pos: 144 Max: 1

Detail - Optional

Loop: LM Elements: 1

User Option (Usage): Used

Purpose: To transmit standard code list identification information

Comments: 

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

DLMS Note:

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LM01 559 Agency Qualifier Code

Description: Code identifying the agency

assigning the code values

M ID 2/2 Must use 1

Code Name

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

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

004010F870S4SA37 24 September 22, 2023

LQ Industry Code Pos: 145 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:

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

2. Code lists at this level are intended to be applicable to the document number level (i.e. do not differ by suffix for split shipments). This is

intended to support a future DLMS enhancement which would accommodate multiple supply status transactions within a single transmission

of the 870S. At this time, only a single supply status may be transmitted per transaction set.

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

Code Name

0 Document Identification Code

DLMS Note:

Use a second iteration to indicate multiple DICs are applicable for combination supply status with direct

delivery notice (DIC AE_ and DIC AB_). (Refer to ADC 465)

67 Type of Assistance Code

DLMS Note:

1. For Security Assistance (SA) transactions, use when the coded address in the transaction number

does not identify the type of assistance and financing.

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

78 Project Code

79 Priority Designator Code

DLMS Note:

Recommend using in all requisitions.

85 Country and Activity Code

DLMS Note:

1. Use to identify the Security Cooperation Customer Code.

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

89 Cooperative Logistics Program Support Code

DLMS Note:

1. For Security Assistance (SA) transactions, use when the coded address in the transaction number

does not identify the type of assistance and financing.

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

95 Offer and Release Option Code

DLMS Note:

1. For Security Assistance (SA) transactions, use when the coded address in the transaction number

does not identify the type of assistance and financing.

2. DLMS enhancement; see introductory DLMS note 3a.
DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

Code Name

004010F870S4SA37 25 September 22, 2023

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.

A1 Ownership Code

DLMS Note:

Use only on supply status subsequent to a referral order to initiate an inter-Service ammunition or

ammunition-related ownership transfer with no physical movement of materiel. Use to identify the

new/gaining (to) ownership code. DLMS enhancement. Refer to ADC 1020.

A2 Customer Within Country Code

DLMS Note:

1. For Security Assistance (SA) transactions, use when the coded address in the transaction number

does not identify the type of assistance and financing.

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

A3 Delivery Term Code

DLMS Note:

1. For Security Assistance (SA) transactions, use when the coded address in the transaction number

does not identify the type of assistance and financing.

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

A4 Case Designator Number

DLMS Note:

Must use in FMS transactions to identify the FMS case number. For Cooperative Logistics Supply

Support Arrangements (CLSSAs), repeat up to two times to identify the FMS Foreign Military Services

Order (FMSO) I and FMSO II case numbers. In this instance, the first occurrence will cite the FMSO I

case number, and a second occurrence, if applicable, will reflect the FMSO II case number.

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

A5 Subcase Number

DLMS Note:

1. Use in FMS transactions based on Service requirements.

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

A6 Freight Forwarder Number

DLMS Note:

1. Must use in FMS transactions to identify the country representative or freight forwarder to receive

shipments and documentation.

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

A7 Record Control Number

DLMS Note:

1. Must use in MAP/GA transactions to identify the program line item number.

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

A8 Program Year Code

DLMS Note:

1. Must use in MAP/GA transactions to indicate the program year in which the requisitioned item was

approved and funded.

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

A9 Supplemental Data

DLMS Note:

1. Use to identify supplementary address/supplemental data.

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

MILSTRIP Supplementary Address (SUPADD) field. During this time, field size is restricted to 6 
DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

Code Name

004010F870S4SA37 26 September 22, 2023

positions; see introductory DLMS note 3d.

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

introductory DLMS note 3a.

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

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

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

5. During legacy MILSTRIP/DLMS transition, use on a supply status for inter-Service ammunition or

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

Signal Code M in conjunction with the supplemental data field constructed as follows: Service/Agency

Code Y followed by the old (from) ownership code, the RIC to which ownership is transferred, and the

new/gaining (to) ownership code. Refer to ADC 1020.

positions; see introductory DLMS note 3d.

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

introductory DLMS note 3a.

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

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

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

5. During legacy MILSTRIP/DLMS transition, use on a supply status for inter-Service ammunition or

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

Signal Code M in conjunction with the supplemental data field constructed as follows: Service/Agency

Code Y followed by the old (from) ownership code, the RIC to which ownership is transferred, and the

new/gaining (to) ownership code. Refer to ADC 1020.

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

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. DLMS enhancement; see introductory DLMS note 3a.

DE Signal Code

DF Media and Status Code

EC Certification Requirements Code

DLMS Note:

1. Must use in MAP/GA transactions to indicate the program year in which the requisitioned item was

approved and funded.

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

GQ Group Qualifier Code

DLMS Note:

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

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

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

without action.

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

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

23-110, Volumes 1 and 2.

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

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

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

without action.

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

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

23-110, Volumes 1 and 2.

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

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

Code Name

004010F870S4SA37 27 September 22, 2023

RD Property Ownership Type Code

DLMS Note:

Use only on supply status subsequent to a referral order to initiate an inter-Service ammunition or

ammunition-related ownership transfer with no physical movement of materiel. Use to identify the old

(from) ownership code. DLMS enhancement. Refer to ADC 1020.

ALP Alteration Lookup

DLMS Note:

Use for the second occurrence of the Priority Designator (PD) by DAAS/GSA when providing BK status

identifying unauthorized use of the PD. The second occurrence will be the original (higher) PD as

assigned by the customer. When used, the PD (qualifier 79) must be present identifying the actual

priority used to process the requisition. An ANSI data maintenance request has been prepared to

establish a new data element 1270 code qualifier assignment for Submitter’s Priority Designator

(Downgraded). This is an authorized DLMS enhancement. (Refer to ADC 279)

Use for the second occurrence of the Priority Designator (PD) by DAAS/GSA when providing BK status

identifying unauthorized use of the PD. The second occurrence will be the original (higher) PD as

assigned by the customer. When used, the PD (qualifier 79) must be present identifying the actual

priority used to process the requisition. An ANSI data maintenance request has been prepared to

establish a new data element 1270 code qualifier assignment for Submitter’s Priority Designator

(Downgraded). This is an authorized DLMS enhancement. (Refer to ADC 279)

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

SEC Stock Exchange Code

DLMS Note:

Use to identify the Exchange Pricing Indicator for intra-Army transactions to identify that the Customer

and NIIN on the transaction are Exchange Pricing relevant. When applicable, cite code value EP

(Exchange Pricing). Refer to ADC 274.

A data maintenance action was approved in version 6010. The approved code/name is “EPI - Exchange

Pricing Indicator".

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)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

004010F870S4SA37 28 September 22, 2023

PO1 Baseline Item Data Pos: 150 Max: 1

Detail - Optional

Loop: PO1 Elements: 15

User Option (Usage): Must use

Purpose: To specify basic and most frequently used line item data

Syntax Rules: 

1. C0302 - If PO103 is present, then PO102 is required.

2. C0504 - If PO105 is present, then PO104 is required.

3. P0607 - If either PO106 or PO107 is present, then the other is required.

4. P0809 - If either PO108 or PO109 is present, then the other is required.

5. P1011 - If either PO110 or PO111 is present, then the other is required.

6. P1213 - If either PO112 or PO113 is present, then the other is required.

7. P1415 - If either PO114 or PO115 is present, then the other is required.

8. P1617 - If either PO116 or PO117 is present, then the other is required.

9. P1819 - If either PO118 or PO119 is present, then the other is required.

10. P2021 - If either PO120 or PO121 is present, then the other is required.

11. P2223 - If either PO122 or PO123 is present, then the other is required.

12. P2425 - If either PO124 or PO125 is present, then the other is required.

Comments: 

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

2. PO101 is the line item identification.

3. PO106 through PO125 provide for ten different product/service IDs per each item. For example: Case, Color, Drawing No., U.P.C. No.,

ISBN No., Model No., or SKU.

DLMS Note:

1. Must use this 2/PO1/150 loop to identify the materiel and status associated with the transaction number. 

2. Use multiple iterations of the 2/PO1/150 loop to identify multiple actions taken on a single transaction. Use a suffix code to differentiate

each loop.

3. Multiple iterations differentiated by status code is a DLMS enhancement which is not supported at this time.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

PO101 350 Assigned Identification

Description: Alphanumeric characters

assigned for differentiation within a

transaction set

DLMS Note: Use to identify a suffix code

associated with the materiel and quantity

for which status is provided. Use

alphabetic characters based on suffix code

assignment rules.

DLMS Note: Use to identify a suffix code

associated with the materiel and quantity

for which status is provided. Use

alphabetic characters based on suffix code

assignment rules.

O AN 1/20 Used 1

PO102 330 Quantity Ordered

Description: Quantity ordered

DLMS Note: 1. Must use to identify the

quantity for which status is being provided.

2. Express as a whole number with no

decimal.

3. A field size exceeding 5 positions (seven

for FSG 13, ammunition) may not be

received or understood by recipient's

automated processing system. See 

X R 1/15 Must use 1
DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F870S4SA37 29 September 22, 2023

introductory DLMS note 3d.

PO103 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 identify the correct

unit of issue associated with the status

provided.

2. DLMS users see the Unit of Issue and

Purchase Unit Conversion Table for

available codes.

O ID 2/2 Used 1

PO104 212 Unit Price

Description: Price per unit of product,

service, commodity, etc.

X R 1/17 Used 1

PO105 639 Basis of Unit Price Code

Description: Code identifying the type of

unit price for an item

DLMS Note: 1. Use to identify the correct

unit price associated with the status

provided.

2. A field size exceeding 7 positions (5

digits dollars and 2 digits cents) may not be

received or understood by the recipient’s

automated processing system.

 3. DLMS transactions authorize an

expanded unit price field size of 9 digits for

dollars and 2 digits for cents. The decimal

point is passed in the transaction. If

conversion to MILS legacy format is

required, unit prices exceeding the legacy

field size constraint will not be perpetuated. 

Authorized DLMS migration enhancement;

see introductory DLMS 3f. Refer to ADC

221A.

3. DLMS transactions authorize an

expanded unit price field size of 9 digits for

dollars and 2 digits for cents. The decimal

point is passed in the transaction. If

conversion to MILS legacy format is

required, unit prices exceeding the legacy

field size constraint will not be perpetuated. 

Authorized DLMS migration enhancement;

see introductory DLMS 3f. Refer to ADC

221A.

O ID 2/2 Used 1

Code Name

ES Estimated

DLMS Note:

Use to indicate the estimated unit price billed when Code ST does not apply.

QT Quoted

DLMS Note:

1. Use to provide the estimated or actual unit cost for the repair service provided for FMS items

repaired/replaced under a repair/return or repair/replace program. Authorized DLMS enhancement. 

See ADC 1031.

2. The Repair Service Value is structured as 9 digits for dollars and 2 digits for cents. The decimal

point is passed in the transaction.

ST Standard

DLMS Note:

Use to identify the standard unit price billed for the materiel.

UM Price per Unit of Measure

DLMS Note:

1. Use with Unit of Use Indicator (BSR11=ZZ) to identify the unit price applicable to the unit of use.

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

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

004010F870S4SA37 30 September 22, 2023

PO106 235 Product/Service ID Qualifier

Description: Code identifying the

type/source of the descriptive number used

in Product/Service ID (234)

DLMS Note: Use one of codes A2, A4, FB,

FS, FT, MG, SW, YP , ZR or ZZ to identify

the materiae which will be provided as

indicated by the status code. Must use the

National Stock Number (NSN) when known,

except when appropriate brand name

subsistence items are identified by the

Subsistence Identification Number or when

maintenance/industrial activity materiel is

identified by Local Stock Number or

Material Control Tracking (MCT) Tag

Number.

DLMS Note: Use one of codes A2, A4, FB,

FS, FT, MG, SW, YP , ZR or ZZ to identify

the materiae which will be provided as

indicated by the status code. Must use the

National Stock Number (NSN) when known,

except when appropriate brand name

subsistence items are identified by the

Subsistence Identification Number or when

maintenance/industrial activity materiel is

identified by Local Stock Number or

Material Control Tracking (MCT) Tag

Number.

X ID 2/2 Must use 1

Code Name

A2 Department of Defense Identification Code (DoDIC)

DLMS Note:

Use to identify ammunition items.

DLMS enhancement

A4 Subsistence Identification Number

DLMS Note:

Use to identify subsistence items.

FB Form Number

DLMS Note:

Use to identify the form stock number.

DLMS enhancement

FS National Stock Number

DLMS Note:

Use to identify the NSN.

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.

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

stock number field. During this time, field length is restricted to 15 positions; field size is expanded to

32 positions for DoD EMALL/part-numbered catalog orders.

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.

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

stock number field. During this time, field length is restricted to 15 positions; field size is expanded to

32 positions for DoD EMALL/part-numbered catalog orders.

SW Stock Number

DLMS Note:

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

2. When used for a unit of use LSN (with 1/BSR11/20=ZZ), the applicable NSN will be included for

cross-reference (at P0110-11). May also be used for identification of LSNs assigned for part-numbered

item requisitioning.

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

YP Publication Number

DLMS Note:
DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

Code Name

004010F870S4SA37 31 September 22, 2023

Use to identify the publication stock number.

DLMS enhancement

ZR Service Control Identification

DLMS Note:

1. Use to identify Material Control Tracking (MCT) Tag Number. 

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

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.

PO107 234 Product/Service ID

Description: Identifying number for a

product or service

X AN 1/48 Must use 1

PO108 235 Product/Service ID Qualifier

Description: Code identifying the

type/source of the descriptive number used

in Product/Service ID (234)

X ID 2/2 Used 1

Code Name

CN Commodity Name

DLMS Note:

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

MB Measurement Type Code

DLMS Note:

1. Use to identify the original requested unit of issue associated with the status provided.

2. Use in next available product/service pair. 

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

Original Unit of Issue".

ZB Commercial and Government Entity (CAGE) Code

DLMS Note:

1. Use with PO106 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.

PO109 234 Product/Service ID

Description: Identifying number for a

product or service

X AN 1/48 Used 1

PO110 235 Product/Service ID Qualifier

Description: Code identifying the

type/source of the descriptive number used

in Product/Service ID (234)

X ID 2/2 Used 1

Code Name

FS National Stock Number

DLMS Note:

1. Use to identify the NSN. 

2. The NSN is provided as a cross-reference when unit of use indicator is included (1/BSR11/20=ZZ)

and the Local Stock Number (LSN) is identified as the primary materiel identification. Authorized DLMS

enhancement under DLA industrial activity support agreement.
DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

004010F870S4SA37 32 September 22, 2023

PO111 234 Product/Service ID

Description: Identifying number for a

product or service

X AN 1/48 Used 1

PO112 235 Product/Service ID Qualifier

Description: Code identifying the

type/source of the descriptive number used

in Product/Service ID (234)

X ID 2/2 Used 1

Code Name

MG Manufacturer's Part Number

DLMS Note:

Use with Supply Status BV to provide the manufacture’s part number when the primary materiel

identification is by NSN (P0106, Code FS). (Refer to ADC 465)

PO113 234 Product/Service ID

Description: Identifying number for a

product or service

X AN 1/48 Used 1

PO114 235 Product/Service ID Qualifier

Description: Code identifying the

type/source of the descriptive number used

in Product/Service ID (234)

X ID 2/2 Used 1

Code Name

ZB Commercial and Government Entity (CAGE) Code

DLMS Note:

Use with manufacturer’s part number (P0112, Code MG) to provide the manufacturer’s CAGE.

PO115 234 Product/Service ID

Description: Identifying number for a

product or service

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

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

004010F870S4SA37 33 September 22, 2023

ISR Item Status Report Pos: 210 Max: 1

Detail - Optional

Loop: ISR Elements: 1

User Option (Usage): Must use

Purpose: To specify detailed purchase order/item status

Semantics: 

1. If ISR01 specifies a date, ISR02 is required.

DLMS Note:

Must use the 2/ISR/210 loop to provide detailed status information.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

ISR01 368 Shipment/Order Status Code

Description: Code indicating the status of

an order or shipment or the disposition of

any difference between the quantity

ordered and the quantity shipped for a line

item or transaction

M ID 2/2 Must use 1

Code Name

CO Customer Inquiry - Unshipped Items Only

DLMS Note:

Use to indicate status in response to a customer follow up or cancellation.

UR Unsolicited Report

DLMS Note:

Use to indicate supply source initiated status not produced in response to customer follow up or

cancellation.
DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

004010F870S4SA37 34 September 22, 2023

QTY Quantity Pos: 230 Max: 4

Detail - Optional

Loop: ISR Elements: 2

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 in 1/BSR01/020 Code 5 supply status transactions to identify the vendor's minimum order quantity.

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

57 Minimum Order Quantity

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

X R 1/15 Must use 1
DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

004010F870S4SA37 35 September 22, 2023

DTM Date/Time Reference Pos: 240 Max: 10

Detail - Optional

Loop: ISR 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 to identify dates associated with the transaction.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

DTM01 374 Date/Time Qualifier

Description: Code specifying type of date

or time, or both date and time

M ID 3/3 Must use 1

Code Name

035 Delivered

DLMS Note:

1. Use with Status Code NW to identify the date materiel is delivered from the Materiel Processing

Center (MPC) to the Navy vessel (signature date).

2. Use with Status Code PD to identify the date materiel is delivered to the artisan by the local industrial

activity worksite. Applies to DLA/Navy industrial activity support agreement. Refer to ADC 379.

050 Received

DLMS Note:

Use with Status Code NL to identify the date materiel is received at the Materiel Processing Center

(MPC) for temporary storage pending delivery to the Navy vessel.

169 Product Availability Date

DLMS Note:

Use with status code BL to identify the date the Notice of Availability was forwarded to the country

representative or freight forwarder.

268 End Date of Support

DLMS Note:

1. Use to identify the Engineering Support Activity Response Due Date. 

2. Use in conjunction with Supply Status PW to indicate the date established by the IMM/ICP waiting for

a response from the Engineering Support Activity. A revised date may be provided in a second

transmission of Supply Status PW if additional time is required to coordinate with the ESA.

3. Authorized DLMS enhancement; refer to ADC 1049.

369 Estimated Departure Date

DLMS Note:

Use to identify the Estimated Shipping Date (ESD) associated with the transaction.

372 Actual Arrival Date

DLMS Note:

Use with Status Code PA to identify the date materiel has arrived at the local industrial activity worksite

and is ready for delivery to artisan. Applies to DLA/Navy industrial activity support agreement. Refer to

ADC 379.

373 Order Start

DLMS Note:
DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

Code Name

004010F870S4SA37 36 September 22, 2023

Use with status code CV to indicate the effective date for requisitioning.

514 Transferred

DLMS Note:

Use with Status Code NY to identify the date that a Material Processing Center (MPC) transships

materiel to another MPC.

996 Required Delivery

DLMS Note:

Use with Supply Status BV to indicate Contract Required Delivery Date. This date may differ from the

customer’s required delivery date. (Refer to ADC 465)

DTM02 373 Date

Description: Date expressed as

CCYYMMDD

X DT 8/8 Must use 1

DTM03 337 Time

Description: Time expressed in 24-hour

clock time as follows: HHMM, or HHMMSS,

or HHMMSSD, or HHMMSSDD, where H =

hours (00-23), M = minutes (00-59), S =

integer seconds (00-59) and DD = decimal

seconds; decimal seconds are expressed

as follows: D = tenths (0-9) and DD =

hundredths (00-99)

DLMS Note: 1. Use when providing MPC

receipt or delivery status to provide the

associated time.

2. Use when providing local industrial

activity worksite arrival and delivery status

to provide the associated time.

3. Express the originating activity's time in

UTC.

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

format.

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

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

004010F870S4SA37 37 September 22, 2023

REF Reference Identification Pos: 300 Max: 12

Detail - Optional

Loop: ISR Elements: 3

User Option (Usage): Used

Purpose: To specify identifying information

Syntax Rules: 

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

Semantics: 

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

DLMS Note:

1. Use for supply status transactions to identify the federal supply schedule number associated with the status provided.

2. Use to provide the narrative explanation associated with the status provided.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

REF01 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

DLMS Note: The following codes are

authorized.

M ID 2/3 Must use 1

Code Name

L1 Letters or Notes

DLMS Note:

 Use to provide the narrative explanation associated with the status provided.

W6 Federal Supply Schedule Number

REF02 127 Reference Identification

Description: Reference information as

defined for a particular Transaction Set or

as specified by the Reference Identification

Qualifier

X AN 1/30 Used 1

REF03 352 Description

Description: A free-form description to

clarify the related data elements and their

content

DLMS Note: Use with code L1 and status

code CA to indicate the reason for rejection.

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

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

004010F870S4SA37 38 September 22, 2023

LM Code Source Information Pos: 320 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/320 loop to identify status and other coded information related to the transaction number.

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)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

004010F870S4SA37 39 September 22, 2023

LQ Industry Code Pos: 330 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:

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

2. Code lists at this level are intended to be applicable to the suffix code level (i.e. may differ by suffix for split shipments). This is intended

to support a future DLMS enhancement which would accommodate multiple supply status transactions within a single transmission of the

870S. At this time, only a single supply status may be transmitted per transaction set.

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

Code Name

79 Priority Designator Code

DLMS Note:

Priority Designator is not used at this level at this time. This data element may differ by suffix, and so

will be available at a future date when multiple supply status by suffix is provided within a single

transmission.

81 Status Code

DLMS Note:

1. Use to identify the supply status associated with the transaction document number/suffix.

2. Multiple repetitions to identify all applicable supply status codes is a DLMS enhancement; see

introductory DLMS note 3a.

83 Supply Condition Code

84 Management Code

DLMS Note:

1. Use to identify the applicable management code associated with the status code.

2. Cite Management Code R with Status Code BD when communicating to the customer that a storage

site denial has occurred against an MRO. The status transaction will be for the denied quantity and

suffix. Authorized for use on an intra-Army basis (ADC 191), and subsequently expanded for

inter-Service/Agency use (ADC 312).

3. Authorized DLMS enhancement under DLA industrial activity support agreement. (Refer to ADC 352,

ADC 359 and ADC 375).

4. Use of multiple repetitions to identify all applicable supply status codes is a prospective future DLMS

enhancement; see introductory DLMS note 3a.

1. Use to identify the applicable management code associated with the status code.

2. Cite Management Code R with Status Code BD when communicating to the customer that a storage

site denial has occurred against an MRO. The status transaction will be for the denied quantity and

suffix. Authorized for use on an intra-Army basis (ADC 191), and subsequently expanded for

inter-Service/Agency use (ADC 312).

3. Authorized DLMS enhancement under DLA industrial activity support agreement. (Refer to ADC 352,

ADC 359 and ADC 375).

4. Use of multiple repetitions to identify all applicable supply status codes is a prospective future DLMS

enhancement; see introductory DLMS note 3a.

A9 Supplemental Data

DLMS Note:

1. Use to identify supplemental address/data. 

2. Supplemental address/data is not used at this level at this time. This data element may differ by

suffix, and so will be available at a future date when multiple supply status by suffix is provided within a

single transmission.
DLMS Implementation Convention (IC)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

Code Name

004010F870S4SA37 40 September 22, 2023

3. Supplemental data is a DLMS enhancement; see introductory DLMS note 3a.

AL Special Requirements Code

DLMS Note:

1. Under MILSTRIP, this is carried in the required delivery date field.

2. Special Requirements Code is not used at this level at this time. This data element may differ by

suffix, and so will be available at a future date when multiple supply status by suffix is provided within a

single transmission.

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

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)

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

004010F870S4SA37 41 September 22, 2023

LX Assigned Number Pos: 340 Max: 1

Detail - Optional

Loop: LX Elements: 1

User Option (Usage): Used

Purpose: To reference a line number in a transaction set

DLMS Note:

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

2. Use the 2/LX/340 loop only when this transaction supports the Retail Transportation and Supply Receipt and Acknowledgement

Interchange Standard Base Supply System (SBSS) interface with CMOS to provide the unique item identifier (UII) and/ or serial number

under the Positive Inventory Control (PIC) Nuclear Weapon Related Materiel (NWRM) UIT program. Refer to ADC 407.

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

number.

4. The entire 2/LX//340 loop is a DLMS enhancement. 

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

2. Use the 2/LX/340 loop only when this transaction supports the Retail Transportation and Supply Receipt and Acknowledgement

Interchange Standard Base Supply System (SBSS) interface with CMOS to provide the unique item identifier (UII) and/ or serial number

under the Positive Inventory Control (PIC) Nuclear Weapon Related Materiel (NWRM) UIT program. Refer to ADC 407.

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

number.

4. The entire 2/LX//340 loop is a DLMS enhancement. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LX01 554 Assigned Number

Description: Number assigned for

differentiation within a transaction set

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

iteration, cite numeric 1. In each

subsequent loop iteration, increase

incrementally by 1.

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

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

004010F870S4SA37 42 September 22, 2023

REF Reference Identification Pos: 350 Max: >1

Detail - Optional

Loop: LX Elements: 3

User Option (Usage): Used

Purpose: To specify identifying information

Syntax Rules: 

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

Semantics: 

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

DLMS Note:

1. Use only when this transaction supports the Retail Transportation and Supply Receipt and Acknowledgement Interchange SBSS interface

with CMOS to provide the UII and/or serial number under the PIC NWRM UIT program

2. This transaction will support item identification based upon the UII or the serial number.

3. Use multiple iterations of 2/REF/350 segment within the 2/LX/340 loop, to provide identifying information for an item 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

M ID 2/3 Must use 1

Code Name

SE Serial Number

DLMS Note:

1. Use to identify the serial number. The serial number may not exceed 30 characters in accordance

with IUID policy.

2. Serial number may be used alone for legacy items when UII is not assigned, otherwise use two

occurrences of this segment to identify both the serial number and the UII. A maximum of 60 items

may be identified for the CMOS interface. Refer to ADC 407.

U3 Unique Supplier Identification Number (USIN)

DLMS Note:

1. Use to identify the UII. The UII may not exceed 50 characters in accordance with IUID policy. A data

maintenance action was approved in version 5020. The approved code/name is "UII - Department of

Defense Unique Item Identifier.”

2. A maximum of 60 items may be identified for the CMOS interface. Refer to ADC 407.

REF02 127 Reference Identification

Description: Reference information as

defined for a particular Transaction Set or

as specified by the Reference Identification

Qualifier

DLMS Note: Use to indicate serial number

when REF01=SE.

O AN 1/30 Used 1

REF03 352 Description

Description: A free-form description to

clarify the related data elements and their

content

DLMS Note: Use to indicate UII value when

REF01=U3.

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

870S Supply Status

ADC 77, 95, 191, 193, 221, 221A, 229, 274, 284, 284A, 279, 312, 352, 375, 379, 381, 388, 407, 436, 441, 441A,

448, 448B, 455A, 465, 466, 1009A, 1014, 1020, 1031, 1043C, 1049, 1068, 1110, 1136, 1161A, 1279, 1287, 1367,

1370, 1412, 1420 and 1454 DLM 4000.25

004010F870S4SA37 43 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