DLMS Implementation Convention (IC) 830W War Materiel Requirements ADC 77, 150, 436, 1043C, 1287, 1367 and 1412 DLM 4000.25

004010F830W1WA05 1 March 1, 2022

830 Planning Schedule with Release Capability

Functional Group=PS

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Planning Schedule with Release

Capability Transaction Set (830) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be

used to provide for customary and established business practice relative to the transfer of forecasting/material release information between

organizations.The planning schedule transaction may be used in various ways or in a combination of ways, such as: (1) a simple forecast; (2) a

forecast with the buyer's authorization for the seller to commit to resources, such as labor or material; (3) a forecast that is also used as an

order release mechanism, containing such elements as resource authorizations, period-to-date cumulative quantities, and specific ship/delivery

patterns for requirements that have been represented in "buckets," such as weekly, monthly, or quarterly. The order release forecast may also

contain all data related to purchase orders, as required, because the order release capability eliminates the need for discrete generation of

purchase orders.

DLMS Note:

1. Organizations use this transaction set to report war reserve materiel (WRM) requirements data to integrated material managers

(IMMs)/inventory control points (ICPs). Use a single occurrence of this transaction set to transmit war reserve materiel requirements to one

or more organizations. Additionally, use one occurrence of this transaction set to transmit a single or multiple transactions. 

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 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 Change (PDC) and Approved DLMS Changes (ADCs) listed. PDCs and

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

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

- ADC 150, Revise DLMS Supplement (DS) 830W, War Materiel Requirements, with Administrative Changes

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

Update MILSTRIP/DLMS Documentation Associated with Routing Identifiers

- Organizational Name and Other Non-Substantive (Administrative) Updates Completed on August 05, 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 December 28, 2016

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

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

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

January 09, 2019

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

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

Office (DEDSO) - Completed on March 1, 2022

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

Indicator to Wide Area Workflow

1. Organizations use this transaction set to report war reserve materiel (WRM) requirements data to integrated material managers

(IMMs)/inventory control points (ICPs). Use a single occurrence of this transaction set to transmit war reserve materiel requirements to one

or more organizations. Additionally, use one occurrence of this transaction set to transmit a single or multiple transactions. 

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 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 Change (PDC) and Approved DLMS Changes (ADCs) listed. PDCs and

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

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

- ADC 150, Revise DLMS Supplement (DS) 830W, War Materiel Requirements, with Administrative Changes

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

Update MILSTRIP/DLMS Documentation Associated with Routing Identifiers

- Organizational Name and Other Non-Substantive (Administrative) Updates Completed on August 05, 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 December 28, 2016

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

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

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

January 09, 2019

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

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

Office (DEDSO) - Completed on March 1, 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 BFR Beginning Segment for Planning

Schedule

M 1 Must use

* 25 XPO Preassigned Purchase Order

Numbers

O >1 Not Used

* 40 CUR Currency O 1 Not Used

* 50 REF Reference Identification O 12 Not Used

* 60 PER Administrative Communications O 3 Not Used
DLMS Implementation Convention (IC) 830W War Materiel Requirements ADC 77, 150, 436, 1043C, 1287, 1367 and 1412 DLM 4000.25

Pos Id Segment Name Req Max Use Repeat Notes Usage

004010F830W1WA05 2 March 1, 2022

Contact * 70 TAX Tax Reference O 3 Not Used

* 80 FOB F.O.B. Related Instructions O 1 Not Used

* 90 CTP Pricing Information O 25 Not Used

* 100 SAC Service, Promotion, Allowance, or

Charge Information

O 25 Not Used

* 110 CSH Sales Requirements O 1 Not Used

* 120 ITD Terms of Sale/Deferred Terms of

Sale

O 2 Not Used

* 130 DTM Date/Time Reference O 10 Not Used

* 140 PID Product/Item Description O 200 Not Used

* 150 MEA Measurements O 40 Not Used

* 160 PWK Paperwork O 25 Not Used

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

* 180 TD1 Carrier Details (Quantity and

Weight)

O 2 Not Used

* 190 TD5 Carrier Details (Routing

Sequence/Transit Time)

O 12 Not Used

* 200 TD3 Carrier Details (Equipment) O 12 Not Used

* 210 TD4 Carrier Details (Special Handling,

or Hazardous Materials, or Both)

O 5 Not Used

* 220 MAN Marks and Numbers O 10 Not Used

LOOP ID - N1 LOOP ID - N1 200

230 N1 Name O 1 Must use

* 240 N2 Additional Name Information O 2 Not Used

* 250 N3 Address Information O 2 Not Used

* 260 N4 Geographic Location O 1 Not Used

* 270 REF Reference Identification O 12 Not Used

* 280 PER Administrative Communications

Contact

O 3 Not Used

* 290 FOB F.O.B. Related Instructions O 1 Not Used

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

* 300 LM Code Source Information O 1 Not Used

310 LQ Industry Code M 100 Must use

Detail:

Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - LIN LOOP ID - LIN >1

10 LIN Item Identification M 1 Must use

* 20 UIT Unit Detail O 1 Not Used

21 DTM Date/Time Reference O 10 Must use

* 30 CUR Currency O 1 Not Used

* 60 PO3 Additional Item Detail O 25 Not Used

* 70 CTP Pricing Information O 25 Not Used

* 80 PID Product/Item Description O 1000 Not Used

* 90 MEA Measurements O 40 Not Used

* 100 PWK Paperwork O 25 Not Used

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

* 120 PO4 Item Physical Details O 1 Not Used

* 130 PRS Part Release Status O 1 Not Used

140 REF Reference Identification O 12 Used

* 150 PER Administrative Communications

Contact

O 3 Not Used

* 170 SAC Service, Promotion, Allowance, or

Charge Information

O 25 Not Used
DLMS Implementation Convention (IC) 830W War Materiel Requirements ADC 77, 150, 436, 1043C, 1287, 1367 and 1412 DLM 4000.25

Pos Id Segment Name Req Max Use Repeat Notes Usage

004010F830W1WA05 3 March 1, 2022

* 180 ITD Terms of Sale/Deferred Terms of

Sale

O 2 Not Used

* 190 TAX Tax Reference O 3 Not Used

* 200 FOB F.O.B. Related Instructions O 1 Not Used

* 210 LDT Lead Time O 12 Not Used

* 220 QTY Quantity O >1 N2/220 Not Used

* 230 ATH Resource Authorization O 20 Not Used

* 240 TD1 Carrier Details (Quantity and

Weight)

O 1 Not Used

* 250 TD5 Carrier Details (Routing

Sequence/Transit Time)

O 12 Not Used

* 260 TD3 Carrier Details (Equipment) O 12 Not Used

* 270 TD4 Carrier Details (Special Handling,

or Hazardous Materials, or Both)

O 5 Not Used

* 280 MAN Marks and Numbers O 10 Not Used

* 290 DD Demand Detail O 10 Not Used

* LOOP ID - SLN * LOOP ID - SLN 100

* 300 SLN Subline Item Detail O 1 Not Used

* 310 PID Product/Item Description O 1000 Not Used

* 315 NM1 Individual or Organizational Name O 10 Not Used

LOOP ID - N1 LOOP ID - N1 200

320 N1 Name O 1 Must use

* 330 N2 Additional Name Information O 2 Not Used

* 340 N3 Address Information O 2 Not Used

* 350 N4 Geographic Location O 1 Not Used

* 360 REF Reference Identification O 12 Not Used

* 370 PER Administrative Communications

Contact

O 3 Not Used

* 380 FOB F.O.B. Related Instructions O 1 Not Used

LOOP ID - LM LOOP ID - LM >1

390 LM Code Source Information O 1 Must use

400 LQ Industry Code M 100 Must use

LOOP ID - FST LOOP ID - FST >1 N2/410L N2/410L

410 FST Forecast Schedule O 1 N2/410 Must use

* 415 QTY Quantity O >1 Not Used

420 SDQ Destination Quantity O 50 Used

LOOP ID - LM LOOP ID - LM >1

430 LM Code Source Information O 1 Used

440 LQ Industry Code M 100 Must use

* LOOP ID - SDP * LOOP ID - SDP 260

* 450 SDP Ship/Delivery Pattern O 1 Not Used

* 460 FST Forecast Schedule O 260 Not Used

* LOOP ID - SHP * LOOP ID - SHP 25

* 470 SHP Shipped/Received Information O 1 Not Used

* 480 REF Reference Identification O 5 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/220 QTY is used to specify supplemental quantities relevant to the forecast function. However, QTY is not related to the actual forecast 
DLMS Implementation Convention (IC) 830W War Materiel Requirements ADC 77, 150, 436, 1043C, 1287, 1367 and 1412 DLM 4000.25

004010F830W1WA05 4 March 1, 2022

quantity in the FST segments.

2/410L At least one occurrence of segment FST is required, either in the FST loop or within the SDP loop. These two loops are mutually

exclusive.

2/410 At least one occurrence of segment FST is required, either in the FST loop or within the SDP loop. These two loops are mutually

exclusive.

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

values of the quantities (FST01) for each FST segment.
DLMS Implementation Convention (IC) 830W War Materiel Requirements ADC 77, 150, 436, 1043C, 1287, 1367 and 1412 DLM 4000.25

004010F830W1WA05 5 March 1, 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

830 Planning Schedule with Release Capability

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 by

the originator's application program.

M AN 4/9 Must use 1
DLMS Implementation Convention (IC) 830W War Materiel Requirements ADC 77, 150, 436, 1043C, 1287, 1367 and 1412 DLM 4000.25

004010F830W1WA05 6 March 1, 2022

BFR Beginning Segment for Planning

Schedule

Pos: 20 Max: 1

Heading - Mandatory

Loop: N/A Elements: 8

User Option (Usage): Must use

Purpose: To indicate the beginning of a planning schedule transaction set; whether a ship or delivery based forecast; and related forecast

envelope dates

Syntax Rules: 

1. R0203 - At least one of BFR02 or BFR03 is required.

Semantics: 

1. If BFR01 contains the value "04" (Net Change), BFR09 is required.

2. BFR02 is the identifying number for a forecast assigned by the orderer/purchaser.

3. BFR06 is the forecast horizon start date: The date when the forecast horizon (envelope) begins.

4. BFR07 is the forecast horizon end date: The date when the forecast horizon (envelope) ends.

5. BFR08 is the date forecast generated: The date the forecast data was generated.

6. BFR09 is the date forecast updated: The date the forecast was updated with "net change" data. (Used only when data element 353 in

BFR01 contains the value "04", meaning net change.)

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

BFR01 353 Transaction Set Purpose Code

Description: Code identifying purpose of

transaction set

DLMS Note: DLMS enhancement; see

introductory DLMS note 3a.

M ID 2/2 Must use 1

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

Code Name

00 Original

77 Simulation Exercise

DLMS Note:

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

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

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

documents which affect accountable records.

BFR02 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 X12 syntax requirements.

X AN 1/30 Must use 1

BFR04 675 Schedule Type Qualifier

Description: Code identifying the type of

dates used when defining a shipping or

delivery time in a schedule or forecast

M ID 2/2 Must use 1

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

Code Name

PR Planned Requirement Based

DLMS Note:

Use to indicate that requirements data reflect forecasted requirements.

BFR05 676 Schedule Quantity Qualifier M ID 1/1 Must use 1
DLMS Implementation Convention (IC) 830W War Materiel Requirements ADC 77, 150, 436, 1043C, 1287, 1367 and 1412 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F830W1WA05 7 March 1, 2022

Description: Code identifying the type of

quantities used when defining a schedule

or forecast

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

Code Name

A Actual Discrete Quantities

DLMS Note:

Use to indicate that quantities reflect discrete requirements.

BFR06 373 Date

Description: Date expressed as

CCYYMMDD

DLMS Note: 1. Must use to identify the

forecast period start date.

2. DLMS enhancement; see introductory

DLMS note 3a. 

M DT 8/8 Must use 1

BFR07 373 Date

Description: Date expressed as

CCYYMMDD

DLMS Note: 1. Use to identify the forecast

period end date.

2. DLMS enhancement; see introductory

DLMS note 3a

O DT 8/8 Used 1

BFR08 373 Date

Description: Date expressed as

CCYYMMDD

DLMS Note: 1. Use to identify the

transaction set preparation date. This date

corresponds to the Universal Time

Coordinate (UTC).

2. DLMS enhancement; see introductory

DLMS note 3a.

M DT 8/8 Must use 1

BFR12 783 Planning Schedule Type Code

Description: Code identifying type of

planning schedule used

O ID 2/2 Must use 1

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

Code Name

XF War Reserve Forecast

DLMS Note:

Must use to indicate the transaction is a war reserve materiel requirements forecast.
DLMS Implementation Convention (IC) 830W War Materiel Requirements ADC 77, 150, 436, 1043C, 1287, 1367 and 1412 DLM 4000.25

004010F830W1WA05 8 March 1, 2022

N1 Name Pos: 230 Max: 1

Heading - Optional

Loop: N1 Elements: 4

User Option (Usage): Must use

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

Syntax Rules: 

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

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

Comments: 

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

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

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

DLMS Note:

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N101 98 Entity Identifier Code

Description: Code identifying an

organizational entity, a physical location,

property or an individual

DLMS Note: The following codes are

authorized.

M ID 2/3 Must use 1

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

Code Name

41 Submitter

DLMS Note:

Must use to identify the organization submitting war reserve materiel (WRM) requirements data.

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

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

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

Code Name

FR Message From
DLMS Implementation Convention (IC) 830W War Materiel Requirements ADC 77, 150, 436, 1043C, 1287, 1367 and 1412 DLM 4000.25

Code Name

004010F830W1WA05 9 March 1, 2022

DLMS Note:

Must use to indicate the organization cited in N104 is originating the transaction.
DLMS Implementation Convention (IC) 830W War Materiel Requirements ADC 77, 150, 436, 1043C, 1287, 1367 and 1412 DLM 4000.25

004010F830W1WA05 10 March 1, 2022

LIN Item Identification Pos: 10 Max: 1

Detail - Mandatory

Loop: LIN Elements: 4

User Option (Usage): Must use

Purpose: To specify basic item identification data

Syntax Rules: 

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Semantics: 

1. LIN01 is the line item identification

Comments: 

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

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

ISBN No., Model No., or SKU.

DLMS Note:

1. Must use the 2/LIN/010 loop to identify the type of WRM and information related to the requirement forecast. 

2. Detailed WRM data identifies incremental monthly forecast quantities for a single line item stratified by type of WRM or by type of WRM

and project code.

3. When stratifying only by type of WRM (for other than Pre-Positioned War Reserve (PWR) requirements), use a single iteration of the

2/LM/390 loop to identify a single War Reserve Materiel Requirement Code and use multiple iterations of the 2/FST/410 loop to identify

incremental monthly forecast quantities. Do not use the 2/LM/430 loop. This stratification method requires multiple iterations of the 2/LIN/010

loop for a single line item to identify each type of WRM.

4. When stratifying by type of WRM and project code (for other than PWR requirements), use a single iteration of the 2/LM/390 loop to

identify a single War Reserve Materiel Requirement Code; use multiple iterations of the 2/FST/410 loop to identify incremental monthly

forecast quantities; and use a single iteration of the 2/LM/430 loop for each iteration of the 2/FST/410 loop to identify the project code

associated with the quantity. This stratification method requires multiple iterations of the 2/LIN/010 loop for a single line item to identify each

type of WRM.

5. For PWR forecast requirements, do not use the 2/LM/390 loop to identify the War Reserve Materiel Requirement Code. Instead, use two

iterations of the 2/FST/410 loop to identify applicable incremental monthly forecast quantities; and use a single iteration of the 2/LM/430

loop, for each iteration of the 2/FST/410 loop, to identify the War Reserve Materiel Requirement Code and/or project code associated with

the quantity.

1. Must use the 2/LIN/010 loop to identify the type of WRM and information related to the requirement forecast. 

2. Detailed WRM data identifies incremental monthly forecast quantities for a single line item stratified by type of WRM or by type of WRM

and project code.

3. When stratifying only by type of WRM (for other than Pre-Positioned War Reserve (PWR) requirements), use a single iteration of the

2/LM/390 loop to identify a single War Reserve Materiel Requirement Code and use multiple iterations of the 2/FST/410 loop to identify

incremental monthly forecast quantities. Do not use the 2/LM/430 loop. This stratification method requires multiple iterations of the 2/LIN/010

loop for a single line item to identify each type of WRM.

4. When stratifying by type of WRM and project code (for other than PWR requirements), use a single iteration of the 2/LM/390 loop to

identify a single War Reserve Materiel Requirement Code; use multiple iterations of the 2/FST/410 loop to identify incremental monthly

forecast quantities; and use a single iteration of the 2/LM/430 loop for each iteration of the 2/FST/410 loop to identify the project code

associated with the quantity. This stratification method requires multiple iterations of the 2/LIN/010 loop for a single line item to identify each

type of WRM.

5. For PWR forecast requirements, do not use the 2/LM/390 loop to identify the War Reserve Materiel Requirement Code. Instead, use two

iterations of the 2/FST/410 loop to identify applicable incremental monthly forecast quantities; and use a single iteration of the 2/LM/430

loop, for each iteration of the 2/FST/410 loop, to identify the War Reserve Materiel Requirement Code and/or project code associated with

the quantity.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LIN02 235 Product/Service ID Qualifier

Description: Code identifying the

type/source of the descriptive number used

in Product/Service ID (234)

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

M ID 2/2 Must use 1
DLMS Implementation Convention (IC) 830W War Materiel Requirements ADC 77, 150, 436, 1043C, 1287, 1367 and 1412 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F830W1WA05 11 March 1, 2022

A4, FB, FS, FT, MG, or YP to identify the

materiel. Must use National Stock Number

(NSN) (code FS) when known, except when

appropriate brand name subsistence items

are identified by the Subsistence

Identification Number.

A4, FB, FS, FT, MG, or YP to identify the

materiel. Must use National Stock Number

(NSN) (code FS) when known, except when

appropriate brand name subsistence items

are identified by the Subsistence

Identification Number.

2. When citing a manufacturer's part

number (code MG), always use code ZB to

identify the manufacturer's commercial and

government entity (CAGE) code.

3. The following codes are authorized.

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

Code Name

A2 Department of Defense Identification Code (DoDIC)

DLMS Note:

Use to identify ammunition items.

A4 Subsistence Identification Number

DLMS Note:

Use to identify subsistence items.

F4 Series Identifier

DLMS Note:

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

FB Form Number

DLMS Note:

Use to identify the form stock number.

FS National Stock Number

DLMS Note:

Must use the NSN when known.

MG Manufacturer's Part Number

DLMS Note:

Use to identify nonstandard materiel.

MN Model Number

DLMS Note:

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

SN Serial Number

DLMS Note:

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

YP Publication Number

DLMS Note:

Use to identify the publication stock number.

LIN03 234 Product/Service ID

Description: Identifying number for a

product or service

M AN 1/48 Must use 1

LIN04 235 Product/Service ID Qualifier

Description: Code identifying the

type/source of the descriptive number used

in Product/Service ID (234)

DLMS Note: The following codes are

authorized.

X ID 2/2 Used 1

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

Code Name

ZB Commercial and Government Entity (CAGE) Code
DLMS Implementation Convention (IC) 830W War Materiel Requirements ADC 77, 150, 436, 1043C, 1287, 1367 and 1412 DLM 4000.25

Code Name

004010F830W1WA05 12 March 1, 2022

DLMS Note:

Use with LIN02 code MG to uniquely identify a manufacturer's part number.

LIN05 234 Product/Service ID

Description: Identifying number for a

product or service

X AN 1/48 Used 1
DLMS Implementation Convention (IC) 830W War Materiel Requirements ADC 77, 150, 436, 1043C, 1287, 1367 and 1412 DLM 4000.25

004010F830W1WA05 13 March 1, 2022

DTM Date/Time Reference Pos: 21 Max: 10

Detail - Optional

Loop: LIN Elements: 2

User Option (Usage): Must use

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:

Must use to identify the date of transaction preparation.

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 identify the date of transaction preparation.

DTM02 373 Date

Description: Date expressed as

CCYYMMDD

DLMS Note: DLMS enhancement; see

introductory DLMS note 3a.

X DT 8/8 Must use 1
DLMS Implementation Convention (IC) 830W War Materiel Requirements ADC 77, 150, 436, 1043C, 1287, 1367 and 1412 DLM 4000.25

004010F830W1WA05 14 March 1, 2022

REF Reference Identification Pos: 140 Max: 12

Detail - Optional

Loop: LIN Elements: 2

User Option (Usage): Used

Purpose: To specify identifying information

Syntax Rules: 

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

Semantics: 

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

REF01 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

DLMS Note: The following code is

authorized.

M ID 2/3 Must use 1

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

Code Name

TN Transaction Reference Number

DLMS Note:

Use to identify the transaction 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 Must use 1
DLMS Implementation Convention (IC) 830W War Materiel Requirements ADC 77, 150, 436, 1043C, 1287, 1367 and 1412 DLM 4000.25

004010F830W1WA05 15 March 1, 2022

N1 Name Pos: 320 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/320 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: 2)

Code Name

KA Item Manager

DLMS Note:

Must use to indicate the IMM/ICP.

ZD Party to Receive Reports

DLMS Note:

Use to indicate the organization(s) to receive reports.

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

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,

O ID 2/3 Used 1
DLMS Implementation Convention (IC) 830W War Materiel Requirements ADC 77, 150, 436, 1043C, 1287, 1367 and 1412 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F830W1WA05 16 March 1, 2022

property or an individual

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

Code Name

TO Message To

DLMS Note:

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

transaction.
DLMS Implementation Convention (IC) 830W War Materiel Requirements ADC 77, 150, 436, 1043C, 1287, 1367 and 1412 DLM 4000.25

004010F830W1WA05 17 March 1, 2022

LM Code Source Information Pos: 390 Max: 1

Detail - Optional

Loop: LM Elements: 1

User Option (Usage): Must use

Purpose: To transmit standard code list identification information

Comments: 

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

DLMS Note:

1. Use the 2/LM/390 loop to identify coded information maintained in department or agency documentation.

2. Use the 2/LM/390 loop to stratify forecasts for other than PWR requirements by type of War Reserve Materiel Requirements Code. Cite

the associated quantities in one or more iterations of the 2/FST/410 loop.

3. Do not use to identify the War Reserve Materiel Requirement Code for PWR requirements.

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) 830W War Materiel Requirements ADC 77, 150, 436, 1043C, 1287, 1367 and 1412 DLM 4000.25

004010F830W1WA05 18 March 1, 2022

LQ Industry Code Pos: 400 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: 5)

Code Name

0 Document Identification Code

DLMS Note:

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

2. The DLSS DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLSS/DLMS

environment. Continued support of the DIC in a full DLMS environment will be assessed at a future

date.

79 Priority Designator Code

DLMS Note:

Recommend using in all requisitions.

A9 Supplemental Data

DLMS Note:

1. Use to identify supplemental address/data. 

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

LZ War Reserve Material Requirement Code

DLMS Note:

Must use for other than PWR requirements to identify the type of war reserve requirement for which the

forecast applies.

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) 830W War Materiel Requirements ADC 77, 150, 436, 1043C, 1287, 1367 and 1412 DLM 4000.25

004010F830W1WA05 19 March 1, 2022

FST Forecast Schedule Pos: 410 Max: 1

Detail - Optional

Loop: FST Elements: 4

User Option (Usage): Must use

Purpose: To specify the forecasted dates and quantities

Syntax Rules: 

1. P0607 - If either FST06 or FST07 is present, then the other is required.

2. P0809 - If either FST08 or FST09 is present, then the other is required.

Semantics: 

1. If FST03 equals "F" (indicating flexible interval), then FST04 and FST05 are required. FST04 would be used for the start date of the

flexible interval and FST05 would be used for the end date of the flexible interval.

Comments: 

1. As qualified by FST02 and FST03, FST04 represents either a discrete forecast date, the first date of a forecasted bucket (weekly,

monthly, quarterly, etc.) or the start date of a flexible interval.

2. FST06 qualifies the time in FST07. The purpose of the FST07 element is to express the specific time of day in a 24-hour clock to satisfy

"just-in-time" requirements. As an alternative, the ship/delivery pattern segment (SDP) may be used to define an approximate time, such

as a.m. or p.m.

DLMS Note:

1. Use multiple 2/FST/410 loop iterations to identify incremental monthly forecast quantities for other than PWR requirements associated

with the War Reserve Materiel Requirements Code identified in the 2/LM/390 loop.

2. Use only two iterations of the 2/FST/410 loop when identifying the PWR requirement. One occurrence must include a FST02 code of D

and the second must include a FST02 code of S.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

FST01 380 Quantity

Description: Numeric value of quantity

DLMS Note: Use to identify the monthly

forecast quantity. Express as a whole

number with no decimal.

M R 1/15 Must use 1

FST02 680 Forecast Qualifier

Description: Code specifying the sender's

confidence level of the forecast data or an

action associated with a forecast

DLMS Note: The following codes are

authorized.

M ID 1/1 Must use 1

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

Code Name

D Planning

DLMS Note:

Use for all Other War Reserve Materiel Requirements (OWMR), repairable return, and Pre-positioned

War Reserve Materiel Requirements (PWRMR) (non-protected) transactions to indicate the requirement

reflects a planning requirement forecast.

S Strike Protection

DLMS Note:

Use for all PWRMR (protected) transactions to indicate the requirement reflects a protected

requirement forecast.

FST03 681 Forecast Timing Qualifier

Description: Code specifying interval

grouping of the forecast

M ID 1/1 Must use 1
DLMS Implementation Convention (IC) 830W War Materiel Requirements ADC 77, 150, 436, 1043C, 1287, 1367 and 1412 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F830W1WA05 20 March 1, 2022

DLMS Note: The following codes are

authorized.

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

Code Name

M Monthly Bucket (Calendar Months)

DLMS Note:

Use to indicate quantities are reflected in monthly increments.

FST04 373 Date

Description: Date expressed as

CCYYMMDD

DLMS Note: 1. Use to identify the specific

month of the forecast period for which the

quantity applies. Assume that the first day

of the month applies.

2. DLMS enhancement; see introductory

DLMS note 3a. 

M DT 8/8 Must use 1
DLMS Implementation Convention (IC) 830W War Materiel Requirements ADC 77, 150, 436, 1043C, 1287, 1367 and 1412 DLM 4000.25

004010F830W1WA05 21 March 1, 2022

SDQ Destination Quantity Pos: 420 Max: 50

Detail - Optional

Loop: FST Elements: 3

User Option (Usage): Used

Purpose: To specify destination and quantity detail

Syntax Rules: 

1. P0506 - If either SDQ05 or SDQ06 is present, then the other is required.

2. P0708 - If either SDQ07 or SDQ08 is present, then the other is required.

3. P0910 - If either SDQ09 or SDQ10 is present, then the other is required.

4. P1112 - If either SDQ11 or SDQ12 is present, then the other is required.

5. P1314 - If either SDQ13 or SDQ14 is present, then the other is required.

6. P1516 - If either SDQ15 or SDQ16 is present, then the other is required.

7. P1718 - If either SDQ17 or SDQ18 is present, then the other is required.

8. P1920 - If either SDQ19 or SDQ20 is present, then the other is required.

9. P2122 - If either SDQ21 or SDQ22 is present, then the other is required.

Semantics: 

1. SDQ23 identifies the area within the location identified in SDQ03, SDQ05, SDQ07, SDQ09, SDQ11, SDQ13, SDQ15, SDQ17, SDQ19,

and SDQ21.

Comments: 

1. SDQ02 is used only if different than previously defined in the transaction set.

2. SDQ03 is the store number.

3. SDQ23 may be used to identify areas within a store, e.g., front room, back room, selling outpost, end aisle display, etc. The value is

agreed to by trading partners or industry conventions.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

SDQ01 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. DLMS users see the Unit of

Issue and Purchase Unit Conversion Table

for applicable codes.

2. Future Streamlined data; see

introductory DLMS note 3c.

M ID 2/2 Must use 1

SDQ03 67 Identification Code

Description: Code identifying a party or

other code

DLMS Note: Use any acceptable value to

satisfy X12 mandatory syntax rules.

M AN 2/80 Must use 1

SDQ04 380 Quantity

Description: Numeric value of quantity

DLMS Note: Use any acceptable value to

satisfy X12 mandatory syntax rules.

M R 1/15 Must use 1
DLMS Implementation Convention (IC) 830W War Materiel Requirements ADC 77, 150, 436, 1043C, 1287, 1367 and 1412 DLM 4000.25

004010F830W1WA05 22 March 1, 2022

LM Code Source Information Pos: 430 Max: 1

Detail - Optional

Loop: LM Elements: 1

User Option (Usage): Used

Purpose: To transmit standard code list identification information

Comments: 

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

DLMS Note:

1. Use this 2/LM/430 loop to identify coded information maintained in departmental or agency documentation.

2. Use this 2/LM/430 loop for OWMR and repairable return transactions to stratify monthly forecasts by project code.

3. Use this 2/LM/430 loop for PWR transactions to stratify monthly forecasts by type of WRM and/or project code.

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) 830W War Materiel Requirements ADC 77, 150, 436, 1043C, 1287, 1367 and 1412 DLM 4000.25

004010F830W1WA05 23 March 1, 2022

LQ Industry Code Pos: 440 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: 10)

Code Name

78 Project Code

DLMS Note:

1. Use as needed to identify the applicable war reserve project code.

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

79 Priority Designator Code

DLMS Note:

Recommend using in all requisitions.

A9 Supplemental Data

DLMS Note:

1. Use to identify supplemental address/data. 

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

GQ Group Qualifier Code

DLMS Note:

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

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

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

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

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

23-110, Volumes 1 and 2.

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

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

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

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

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

23-110, Volumes 1 and 2.

LZ War Reserve Material Requirement Code

DLMS Note:

Must use to identify PWR requirement forecast.

COG Cognizance Symbol

DLMS Note:

Use to identify the material cognizance symbol (COG) of the end item. Indicate NSL for non-stock

numbered listed items. This is a Navy-unique data element meaningful to Navy only; Non-Navy

Components are to perpetuate without action.
DLMS Implementation Convention (IC) 830W War Materiel Requirements ADC 77, 150, 436, 1043C, 1287, 1367 and 1412 DLM 4000.25

Code Name

004010F830W1WA05 24 March 1, 2022

IMC Item Management Code

DLMS Note:

Use to identify the Item Management Code (IMC) for integrated material management. 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.

MCC Material Control Code

DLMS Note:

Use to identify the Material Control Code (MCC) for special inventory reporting. 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.

SMI Special Material Identification Code

DLMS Note:

Use to identify the Special Material Identification Code (SMIC) for an 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.

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) 830W War Materiel Requirements ADC 77, 150, 436, 1043C, 1287, 1367 and 1412 DLM 4000.25

004010F830W1WA05 25 March 1, 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