DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

004010F870L2LA12 1 March 15, 2022

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 provide status on Special Program Requirements and to notify the organization originating the

transaction that the Federal Supply Classification (FSC) provided on the original transaction was incorrect. Use a single occurrence of this

transaction set to transmit supply status to one or more organizations. Use one occurrence of this transaction set to transmit a single or

multiple transactions. 

a. Inventory Control Points (ICPs) or Integrated Material Managers (IMMs) use this transaction set to provide Special Program Requirements

(SPR) status on SPR requests (corresponds to MILSTRAP Document Identifier Code (DIC) DYK functionality). Defense Automatic

Addressing System (DAAS) uses this transaction set to notify the organization originating the SPR transaction that the transaction was

rerouted or that the Federal Supply Classification (FSC) in the original transaction was revised (corresponds to MILSTRAP DIC DZ9

functionality).

b. ICPs or IMMs (source of supply) also use this transaction to provide status to a forecasting requirement (accept or reject) for a Demand

Data Exchange (DDE) Projected Gross Demand Plan (GDP), or Army Supply Plan (ASP) (DLMS 830D transaction). 

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. Defense Logistics Standard System (DLSS) data which must be retained in the DLMS for a transition period to support transaction

conversion in a mixed DLSS/DLMS environment. This data will be streamlined out once full DLMS implementation is reached. Components

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

d. Data elements which have an expanded files size above existing DLSS capability which may not be supported by the recipient's

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

4. This revision to the DLMS IC incorporates Proposed DLMS Changes (PDC) and Approved DLMS Changes (ADC) listed. PDCs/ADCs

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

- ADC 287, Administrative Update to DLMS Supplement 830R (Version 4010), Special Program Requirements (SPR), 870L SPR/LASE

Status, and DLMS Manual (Supply/MILSTRAP)

- ADC 333, Revision to DLMS, Volume 2, Chapter for Logistics Asset Support Estimate (LASE); and Administrative Updates to DLMS 846L,

870L, LASE Request Codes and Reject Advice Codes (Supply/MILSTRAP)

- ADC 400, Elimination of the DLMS-MILSTRAP Logistics Asset Support Estimate (LASE) Process no Longer Required by the DOD

Components (DLMS/MILSTRAP/MILSTRIP)

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

Update MILSTRIP/DLMS Documentation Associated with Routing Identifiers

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

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

- Administrative Update to Reflect Realignment to Recognize DLMS Program Office Completed on February 01, 2017

- ADC 1267, Revise DLMS 830D to Accommodate Navy Fleet Readiness Centers (FRC) Gross Demand Plan (GDP) for Implementation by

all DOD Components

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

April 09, 2019

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

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

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

- ADC 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 March 14, 2022

1. Organizations use this transaction set to provide status on Special Program Requirements and to notify the organization originating the

transaction that the Federal Supply Classification (FSC) provided on the original transaction was incorrect. Use a single occurrence of this

transaction set to transmit supply status to one or more organizations. Use one occurrence of this transaction set to transmit a single or

multiple transactions. 

a. Inventory Control Points (ICPs) or Integrated Material Managers (IMMs) use this transaction set to provide Special Program Requirements

(SPR) status on SPR requests (corresponds to MILSTRAP Document Identifier Code (DIC) DYK functionality). Defense Automatic

Addressing System (DAAS) uses this transaction set to notify the organization originating the SPR transaction that the transaction was

rerouted or that the Federal Supply Classification (FSC) in the original transaction was revised (corresponds to MILSTRAP DIC DZ9

functionality).

b. ICPs or IMMs (source of supply) also use this transaction to provide status to a forecasting requirement (accept or reject) for a Demand

Data Exchange (DDE) Projected Gross Demand Plan (GDP), or Army Supply Plan (ASP) (DLMS 830D transaction). 

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. Defense Logistics Standard System (DLSS) data which must be retained in the DLMS for a transition period to support transaction

conversion in a mixed DLSS/DLMS environment. This data will be streamlined out once full DLMS implementation is reached. Components

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

d. Data elements which have an expanded files size above existing DLSS capability which may not be supported by the recipient's

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

4. This revision to the DLMS IC incorporates Proposed DLMS Changes (PDC) and Approved DLMS Changes (ADC) listed. PDCs/ADCs

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

- ADC 287, Administrative Update to DLMS Supplement 830R (Version 4010), Special Program Requirements (SPR), 870L SPR/LASE

Status, and DLMS Manual (Supply/MILSTRAP)

- ADC 333, Revision to DLMS, Volume 2, Chapter for Logistics Asset Support Estimate (LASE); and Administrative Updates to DLMS 846L,

870L, LASE Request Codes and Reject Advice Codes (Supply/MILSTRAP)

- ADC 400, Elimination of the DLMS-MILSTRAP Logistics Asset Support Estimate (LASE) Process no Longer Required by the DOD

Components (DLMS/MILSTRAP/MILSTRIP)

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

Update MILSTRIP/DLMS Documentation Associated with Routing Identifiers

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

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

- Administrative Update to Reflect Realignment to Recognize DLMS Program Office Completed on February 01, 2017

- ADC 1267, Revise DLMS 830D to Accommodate Navy Fleet Readiness Centers (FRC) Gross Demand Plan (GDP) for Implementation by

all DOD Components

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

April 09, 2019

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

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

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

- ADC 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 March 14, 2022
DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

004010F870L2LA12 2 March 15, 2022

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

Indicator to Wide Area Workflow

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,

or Hazardous Materials, or Both)

O 1 Not Used

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

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

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

LOOP ID - REF LOOP ID - REF >1

87 REF Reference Identification O 1 Must use

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

LOOP ID - N1 LOOP ID - N1 200

90 N1 Name O 1 Must use

* 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
DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

Pos Id Segment Name Req Max Use Repeat Notes Usage

004010F870L2LA12 3 March 15, 2022

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 Used

* 155 CUR Currency O 1 Not Used

* 160 SLN Subline Item Detail O 100 Not Used

* 170 PO3 Additional Item Detail O 1 Not Used

180 PID Product/Item Description O 1000 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 Used

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

* 350 REF Reference Identification O >1 Not 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 Not Used

Summary:

Pos Id Segment Name Req Max Use Repeat Notes Usage

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

20 SE Transaction Set Trailer M 1 Must use

Notes: 

2/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) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

004010F870L2LA12 4 March 15, 2022

ST Transaction Set Header Pos: 10 Max: 1

Heading - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must use

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

Semantics: 

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

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

ST01 143 Transaction Set Identifier Code

Description: Code uniquely identifying a

Transaction Set

M ID 3/3 Must use 1

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

Code Name

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) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

004010F870L2LA12 5 March 15, 2022

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

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

Code Name

3 Unsolicited Report

DLMS Note:

Status Notification. DLA Transaction Services uses Status Notification transactions to notify the

submitter that an SPR transaction was rerouted or that the FSC changed. (MILSTRAP DIC DZ9

functionality.)

9 Response to a Requirement Forecast

DLMS Note:

1. SPR Status. ICP/IMM uses SPR Status transactions to provide SPR status to a forecasting activity in

response to a DLMS 830R SPR transaction. (MILSTRAP DIC DYK functionality.)

2. For DDE, GDP, ASP status, use to provide status to a forecasting requirement in response to DLMS

830D Demand Data Exchange Projected Supply Plan transaction.

BSR02 847 Order/Item Code

Description: Code identifying a group of

orders and items

M ID 1/2 Must use 1

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

Code Name

CA All Orders - All Items

DLMS Note:

Use to indicate the response applies to all specified items.

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 a mandatory X12 syntax

requirement.

M AN 1/30 Must use 1

BSR04 373 Date

Description: Date expressed as

M DT 8/8 Must use 1
DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F870L2LA12 6 March 15, 2022

CCYYMMDD

DLMS Note: This date is the date of

transaction set preparation and

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

originator's time of transaction set

preparation time in UTC.

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

format.

O TM 4/8 Used 1

BSR11 353 Transaction Set Purpose Code

Description: Code identifying purpose of

transaction set

O ID 2/2 Used 1

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

Code Name

00 Original

77 Simulation Exercise

DLMS Note:

Use to identify a simulated mobilization exercise transaction set. Activities initiating simulated

mobilization exercises must ensure complete coordination with all activities involved. All transaction set

recipients must use extreme caution to ensure that individual transactions do not process as action

documents which affect accountable records.
DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

004010F870L2LA12 7 March 15, 2022

N1 Name Pos: 50 Max: 1

Heading - Optional

Loop: N1 Elements: 4

User Option (Usage): Must use

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

Syntax Rules: 

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

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

Comments: 

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

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

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

DLMS Note:

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, or ZN.

2. The following codes are authorized.

M ID 2/3 Must use 1

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

Code Name

GP Gateway Provider

DLMS Note:

This is DLA Transaction Services. DLA Transaction Services uses when providing Status Notification

that an SPR transaction was rerouted or that the FSC has changed (BSR01 Status Report Code 3.)

Z4 Owning Inventory Control Point

DLMS Note:

1. Use to identify the ICP or IMM providing SPR status (BSR01 Status Report Code 9).

2. Use to identify the source of supply providing DDE, GDP or ASP status (BSR01 Status Report Code

9).

ZN Losing Inventory Manager

DLMS Note:

Use with BSR01 Status Report Code 9 when the LIM is providing SPR 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

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

Code Name

10 Department of Defense Activity Address Code (DODAAC)

DLMS Note:

DLMS enhancement. See introductory DLMS note 3a.
DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

Code Name

004010F870L2LA12 8 March 15, 2022

M4 Department of Defense Routing Identifier Code (RIC)

N104 67 Identification Code

Description: Code identifying a party or

other code

X AN 2/80 Must use 1

N106 98 Entity Identifier Code

Description: Code identifying an

organizational entity, a physical location,

property or an individual

O ID 2/3 Used 1

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

Code Name

FR Message From

DLMS Note:

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

transaction set.
DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

004010F870L2LA12 9 March 15, 2022

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 for SPR transaction status 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

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

Code Name

W Transaction Reference Number

DLMS Note:

Use to identify the individual SPR transaction status loops.
DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

004010F870L2LA12 10 March 15, 2022

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 in SPR status transactions.

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

CodeList Summary (Total Codes: 1112, Included: 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 Used 1
DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

004010F870L2LA12 11 March 15, 2022

REF Reference Identification Pos: 87 Max: 1

Detail - Optional

Loop: REF Elements: 2

User Option (Usage): Must use

Purpose: To specify identifying information

Syntax Rules: 

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

Semantics: 

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

DLMS Note:

Must use to identify the customer assigned transaction number.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

REF01 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

DLMS Note: The following codes are

authorized.

M ID 2/3 Must use 1

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

Code Name

FG Fund Identification Number

DLMS Note:

For Navy use, this is the Program Funding Indicator associated to a Gross Demand Plan (GDP). See

ADC 1267.

TN Transaction Reference Number

DLMS Note:

Must use to identify the customer assigned transaction number. This is the document number.

WL Federal Supply Classification Code

DLMS Note:

Use for Status Notification transactions to identify the correct FSC associated with the materiel cited in

an SPR transaction.

REF02 127 Reference Identification

Description: Reference information as

defined for a particular Transaction Set or

as specified by the Reference Identification

Qualifier

X AN 1/30 Must use 1
DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

004010F870L2LA12 12 March 15, 2022

N1 Name Pos: 90 Max: 1

Detail - Optional

Loop: N1 Elements: 4

User Option (Usage): Must use

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

Syntax Rules: 

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

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

Comments: 

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

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

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

DLMS Note:

1. Must use one iteration of 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

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

Code Name

78 Service Requester

DLMS Note:

Must use to indicate the activity submitting the original SPR transaction.

ZA Corrected Address

DLMS Note:

Use to identify the source of supply to whom DLA Transaction Services has rerouted the transaction.

ZP Gaining Inventory Manager

DLMS Note:

Use for SPR Status transactions to identify the Gaining Item Manager (GIM) for those items of supply

involved in logistics reassignment.

N103 66 Identification Code Qualifier

Description: Code designating the

system/method of code structure used for

Identification Code (67)

X ID 1/2 Must use 1

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

Code Name

10 Department of Defense Activity Address Code (DODAAC)

DLMS Note:

DLMS enhancement. See introductory DLMS note 3a. 

M4 Department of Defense Routing Identifier Code (RIC)

N104 67 Identification Code X AN 2/80 Must use 1
DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F870L2LA12 13 March 15, 2022

Description: Code identifying a party or

other code

N106 98 Entity Identifier Code

Description: Code identifying an

organizational entity, a physical location,

property or an individual

O ID 2/3 Used 1

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

Code Name

TO Message To

DLMS Note:

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

set.
DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

004010F870L2LA12 14 March 15, 2022

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 departmental or agency documentation.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LM01 559 Agency Qualifier Code

Description: Code identifying the agency

assigning the code values

M ID 2/2 Must use 1

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

Code Name

DF Department of Defense (DoD)
DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

004010F870L2LA12 15 March 15, 2022

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:

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LQ01 1270 Code List Qualifier Code

Description: Code identifying a specific

industry code list

DLMS Note: The following codes are

authorized.

O ID 1/3 Must use 1

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

Code Name

0 Document Identification Code

DLMS Note:

Use a second iteration with BSR01 code 3 to identify the DIC of the original transaction for which status

is being provided.

78 Project Code

79 Priority Designator Code

DLMS Note:

Recommend using in all requisitions.

81 Status Code

DLMS Note:

Use multiple repetitions when needed to identify status associated with the transaction number to notify

of an FSC change (Status Code BG) and/or that DLA Transaction Services rerouted an SPR

transaction (Status Code BM); otherwise do not use. Use with Status Notification transactions (BSR01

code 3).

83 Supply Condition Code

A9 Supplemental Data

DLMS Note:

1. Use to identify supplemental address/data.

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

Supplementary Address (SUPAAD) field. During this time, field size is restricted to 6 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 SUPAAD will be reflected

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

1. Use to identify supplemental address/data.

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

Supplementary Address (SUPAAD) field. During this time, field size is restricted to 6 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 SUPAAD will be reflected

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

AJ Utilization Code

DLMS Note:

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

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

ED Coast Designation Code
DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

Code Name

004010F870L2LA12 16 March 15, 2022

GQ Group Qualifier Code

DLMS Note:

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

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

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

without action.

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

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

23-110, Volumes 1 and 2.

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

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

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

without action.

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

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

23-110, Volumes 1 and 2.

COG Cognizance Symbol

DLMS Note:

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

IMC Item Management Code

DLMS Note:

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

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

action.

MCC Material Control Code

DLMS Note:

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

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

SMI Special Material Identification Code

DLMS Note:

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

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

LQ02 1271 Industry Code

Description: Code indicating a code from a

specific industry code list

X AN 1/30 Must use 1
DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

004010F870L2LA12 17 March 15, 2022

PO1 Baseline Item Data Pos: 150 Max: 1

Detail - Optional

Loop: PO1 Elements: 4

User Option (Usage): Used

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:

Use the 2/P01/150 loop for SPR response transactions to identify the materiel and status associated with the transaction number.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

PO106 235 Product/Service ID Qualifier

Description: Code identifying the

type/source of the descriptive number used

in Product/Service ID (234)

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

A4, FB, FS, KD, MG, PR, RR, SR, SW, or

YP to identify the materiel. Must use the

National Stock number (NSN) when known

except when appropriate brand name

subsistence items are identified by the

Subsistence Identification Number.

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

A4, FB, FS, KD, MG, PR, RR, SR, SW, or

YP to identify the materiel. Must use the

National Stock number (NSN) when known

except when appropriate brand name

subsistence items are identified by the

Subsistence Identification Number.

2. The following codes are authorized.

X ID 2/2 Must use 1

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

Code Name

A2 Department of Defense Identification Code (DoDIC)

DLMS Note:

1. Use to identify ammunition items.

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

A4 Subsistence Identification Number

DLMS Note:

1. Use to identify subsistence items.

2. DLMS enhancement. See introductory DLMS note 3a. 
DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

Code Name

004010F870L2LA12 18 March 15, 2022

FB Form Number

DLMS Note:

1. Use to identify the form stock number.

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

FS National Stock Number

KD Replacement National Stock Number

DLMS Note:

Use to identify the substitute or superseding NSN when the requested materiel is either not available or

obsolete.

MG Manufacturer's Part Number

DLMS Note:

1. Use to identify nonstandard materiel.

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

PR Process Number

DLMS Note:

1. Use to identify the substitute or superseding publication number when the requested materiel is

either not available or obsolete.

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

RR Replacement Product Number

DLMS Note:

1. Use to identify the substitute or superseding form stock number when the requested materiel is either

not available or obsolete.

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

SR Substitute Product Number

DLMS Note:

1. Use to identify the substitute or superseding ammunition item when the requested materiel is either

not available or obsolete.

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

SW Stock Number

DLMS Note:

1. Use to identify the substitute or superseding subsistence item when the requested materiel is either

not available or obsolete.

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

TP Product Type Code

DLMS Note:

1. For clothing and footwear, use to identify the NSN when the materiel requested represents a generic

requirement for which the quantity should be distributed across a predefined range of sizes.

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

YP Publication Number

DLMS Note:

1. Use to identify the publication stock number.

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

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

X ID 2/2 Used 1
DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F870L2LA12 19 March 15, 2022

in Product/Service ID (234)

DLMS Note: 1. When P0106 is qualifier

MG, must use P0108 qualifier ZB.

2. The following codes are authorized.

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

Code Name

ZB Commercial and Government Entity (CAGE) Code

DLMS Note:

1. Use with P0106 code MG to uniquely identify a manufacturer’s part number.

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

PO109 234 Product/Service ID

Description: Identifying number for a

product or service

X AN 1/48 Used 1
DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

004010F870L2LA12 20 March 15, 2022

PID Product/Item Description Pos: 180 Max: 1000

Detail - Optional

Loop: PO1 Elements: 2

User Option (Usage): Used

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

Syntax Rules: 

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

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

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

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

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

Semantics: 

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

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

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

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

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

Comments: 

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

used.

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

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

DLMS Note:

1. This segment contains free form text which the DDE submitter may use to provide information of value to the collaboration

participants. The submitter may also use this segment to provide information deemed useful to their planners during collaboration as it will

be available for their viewing in the Collaborate tool. This segment is optional and informational in nature and can be viewed by all

participants in the collaboration process.

2. Use to perpetuate optional field information provided by the originator via DLMS 830D. See ADC 1267.

3. On an interim basis, to accommodate DLA’s DIC CDD format in a mixed DLMS/non-DLMS CDD environment, the free form text in the PID

segment is limited to a total of 110 characters which maps to DIC CDD Optional fields 1 through 4 in record positions 953-1062. To

accommodate DLA DIC CDD fixed format, this requires restricting use of 2/PID/180 segment to a maximum of 4 iterations, with maximum 20

characters each in 3 iterations and maximum of 50 characters in one iteration. This supports DLA DIC CDD which has 3 optional fields of 20

characters and 1 optional field of 50 characters. Use of PID segment, other than as described by this note, is a DLMS enhancement. See

introductory DLMS note 3a.

1. This segment contains free form text which the DDE submitter may use to provide information of value to the collaboration

participants. The submitter may also use this segment to provide information deemed useful to their planners during collaboration as it will

be available for their viewing in the Collaborate tool. This segment is optional and informational in nature and can be viewed by all

participants in the collaboration process.

2. Use to perpetuate optional field information provided by the originator via DLMS 830D. See ADC 1267.

3. On an interim basis, to accommodate DLA’s DIC CDD format in a mixed DLMS/non-DLMS CDD environment, the free form text in the PID

segment is limited to a total of 110 characters which maps to DIC CDD Optional fields 1 through 4 in record positions 953-1062. To

accommodate DLA DIC CDD fixed format, this requires restricting use of 2/PID/180 segment to a maximum of 4 iterations, with maximum 20

characters each in 3 iterations and maximum of 50 characters in one iteration. This supports DLA DIC CDD which has 3 optional fields of 20

characters and 1 optional field of 50 characters. Use of PID segment, other than as described by this note, is a DLMS enhancement. See

introductory DLMS note 3a.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

PID01 349 Item Description Type

Description: Code indicating the format of

a description

M ID 1/1 Must use 1

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

Code Name

F Free-form

DLMS Note:

Use to perpetuate optional information provided by the originator via DLMS 830D. See ADC 1267.

PID05 352 Description

Description: A free-form description to

clarify the related data elements and their

content

O AN 1/80 Used 1
DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F870L2LA12 21 March 15, 2022

DLMS Note: Use with PID01 to provide

narrative information to the collaboration

participants. 
DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

004010F870L2LA12 22 March 15, 2022

ISR Item Status Report Pos: 210 Max: 1

Detail - Optional

Loop: ISR Elements: 1

User Option (Usage): Used

Purpose: To specify detailed purchase order/item status

Semantics: 

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

DLMS Note:

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

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

Code Name

CO Customer Inquiry - Unshipped Items Only

DLMS Note:

Use to indicate status is provided in response to a customer inquiry.

UR Unsolicited Report

DLMS Note:

Use to indicate status is provided in accordance with normal status response parameters.
DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

004010F870L2LA12 23 March 15, 2022

QTY Quantity Pos: 230 Max: 4

Detail - Optional

Loop: ISR Elements: 3

User Option (Usage): Used

Purpose: To specify quantity information

Syntax Rules: 

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

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

Semantics: 

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

DLMS Note:

1. Must use one repetition with responses to SPR forecasts to identify the quantity for which the SPR status code in the 2/LM/320 loop

applies. May use a second repetition in response to an SPR forecast to indicate the procurement leadtime.

2. Do not use with transactions notifying of errors in SPR transactions.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

QTY01 673 Quantity Qualifier

Description: Code specifying the type of

quantity

M ID 2/2 Must use 1

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

Code Name

1G Lead Time (in calendar units)

DLMS Note:

Use to indicate the number of procurement (or assembly) lead time days when required by the

associated status code.

AY Forecast

DLMS Note:

Use to identify the SPR forecast quantity associated with the support date in the 2/DTM/240 segment.

QTY02 380 Quantity

Description: Numeric value of quantity

DLMS Note: 1. Express as a whole

number with no decimals.

2. A field size exceeding 5 positions may

not be received or understood by the

recipient's automated processing system. 

See introductory DLMS note 3d.

X R 1/15 Must use 1

QTY03 C001 Composite Unit of Measure

Description: To identify a composite unit of

measure(See Figures Appendix for

examples of use)

O Comp Used 1

QTY03-01 355 Unit or Basis for Measurement Code

Description: Code specifying the units in

which a value is being expressed, or

manner in which a measurement has been

taken

DLMS Note: DLMS users see the Unit of

Issue and Purchase Unit Conversion Table

for available codes.

M ID 2/2 Must use 1
DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F870L2LA12 24 March 15, 2022
DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

004010F870L2LA12 25 March 15, 2022

DTM Date/Time Reference Pos: 240 Max: 10

Detail - Optional

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

1. Must use with responses to SPR forecasts to identify the support date associated with the forecast quantity in the 2/QTY/230 segment for

which the status in the 2/LM/320 loop is provided.

2. Do not use with transactions notifying of errors in SPR transactions.

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

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

Code Name

106 Required By

DLMS Note:

Use to identify the specific support date for which SPR status is provided.

DTM02 373 Date

Description: Date expressed as

CCYYMMDD

X DT 8/8 Must use 1
DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

004010F870L2LA12 26 March 15, 2022

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 related to the forecast quantity in the 2/QTY/230 segment and the date in the 2/DTM/240 segment.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LM01 559 Agency Qualifier Code

Description: Code identifying the agency

assigning the code values

M ID 2/2 Must use 1

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

Code Name

DF Department of Defense (DoD)
DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

004010F870L2LA12 27 March 15, 2022

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. Use multiple repetitions to identify SPR status associated with the transaction number.

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

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

Code Name

79 Priority Designator Code

DLMS Note:

Recommend using in all requisitions.

A9 Supplemental Data

DLMS Note:

1. Use to identify supplemental address/data.

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

Supplementary Address (SUPAAD) field. During this time, field size is restricted to 6 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 SUPAAD will be reflected

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

1. Use to identify supplemental address/data.

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

Supplementary Address (SUPAAD) field. During this time, field size is restricted to 6 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 SUPAAD will be reflected

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

AJ Utilization Code

DLMS Note:

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

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

DV Demand Planning Status Code

DLMS Note:

1. Local code DV is established for use in the 870L, version 4010. A data maintenance action will be

submitted to establish ‘DV – Demand Planning Status Code’ in a future version.

2. Use to identify the status of a Demand Data Exchange (DDE), Gross Demand Plan (GDP), or Army

Supply Plan (ASP). See DLMS Volume 2, Appendix 7.33 for a full list of authorized codes. See ADC

1267. 

EY Special Program Requirement Status Code

LQ02 1271 Industry Code X AN 1/30 Must use 1
DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F870L2LA12 28 March 15, 2022

Description: Code indicating a code from a

specific industry code list
DLMS Implementation Convention (IC) 870L Demand and Supply Planning 

Status/Notification

ADC 287, 333, 400, 436, 1043C, 1267, 1287, 1367, 1370 and 1412 DLM

4000.25

004010F870L2LA12 29 March 15, 2022

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