1 of 16 

ADC 287 

Attachment 

ATTACHMENT TO ADC 287 

Revision to DLMS 870L, SPR/LASE Status and Corresponding DLMS 

Manual Procedures; Administrative Update to DLMS 830R, SPR 

(Supply/MILSTRAP) 

1. Originator: 

 a. Service/Agency: Defense Logistics Management Standards Office (DLMSO)

 b. Originator: Ms. Mary Jane Johnson, DLMSO, e-mail: Mary.Jane.Johnson@dla.mil

2. FUNCTIONAL AREA: Supply 

3. REFERENCES: 

a. DoD 4000.25-M, DLMS, Volume 2 Supply 

 (http://www.dla.mil/j-6/dlmso/elibrary/manuals/dlms/v2.asp) 

b. DLMSO memorandum, March 6, 2008, subject: PDC 297, Establish DS 830D, Version 

4030, for Demand Data Exchange (DDE) Forecast in Place of DS 830R, Version 4030, Special 

Program Requirements/DDE Forecast (Supply) 

 (http://www.dla.mil/j-6/dlmso/eLibrary/Changes/proposed.asp) 

c. DoD 4000.25-2-M, Military Standard Transaction Reporting and Accounting Procedures 

(MILSTRAP) (http://www.dla.mil/j-6/dlmso/elibrary/Manuals/MILSTRAP/default.asp) 

d. DLMSO memorandum, May 1, 2008, subject: DLMS Supply Process Review Committee 

(PRC) Meeting 08-01, April 8-10, 2008 (available at: http://www.dla.mil/j6/dlmso/Programs/Committees/Supply/supplyPRC.asp) 

4. REQUESTED CHANGE: 

a. Title: Revision to DLMS 870L, SPR/LASE Status and Corresponding DLMS Manual 

Procedures; Administrative Update to DLMS 830R, SPR (Supply/MILSTRAP)

b. Description of Change: 

(1) Updates to DoD 4000.25-M (reference 1a) , DLMS, Volume 2, Chapter 2, as 

revised by PDC 297 (reference 1b): 

(a) Revise DLMS SPR procedures at section C2.2.4 (DAASC Processing) and delete 

current section C2.2.5 (IMM Validation and Rejection of SPR), to bring the DLMS procedures in line 

with the corresponding MILSTRAP (reference 1c) procedural requirement and the existing SPR 

process. The DLMS guidance for editing the NSN field of SPR transactions for Federal Supply Class 
2 of 16 

ADC 287 

Attachment 

(FSC) and National Item Identification Number (NIIN) compatibility conflicts with the MILSTRAP 

chapter 9 guidance. MILSTRAP business rules direct that DAASC will perform the FSC/NIIN 

compatibility check for SPR transactions and DAASC shall generate the associated Status Notification 

Transaction (MILSTRAP DZ9 (or corresponding DLMS 870L)), while the DLMS business rules have the 

IMM performing the FSC/NIIN compatibility check for SPR transactions and generating the 870L Status 

Notification Transaction. This update removes the disconnect between the MILSTRAP and DLMS 

procedures. 

(b) PDC 301 included an administrative update to move the War Materiel 

Requirements procedures from DLMS, Volume 2, Chapter 3 into Volume 2, Chapter 2 so that 

all DLMS forecasting processes are in one chapter: SPR, Demand Data Exchange (DDE), and 

WMR. However the MILSTRAP Administrator is electing not to make that administrative 

update at this time. As discussed at Supply Process Review Committee Meeting 08-2 

(reference 3.d) DLMSO is investigating the possibility of combining the DLSS and DLMS 

manuals since the current process of maintaining two sets of publications is resource intensive, 

duplicative in nature, and no longer practical. If the manuals are combined, that process will 

impact how the chapters are structured. The administrative updates to the WMR chapter 

identified by PDC 303 will be incorporated in DLMS, Volume 2, Chapter 3 by this ADC.

(2) DLMS Supplements 870L and 830R: 

(a) Update DS 870L to support elimination of the MILSTRAP/DLMS procedural 

incompatibility noted above; 

 (b) Update DS 830R and 870L to identify the correlation to the corresponding 

MILSTRAP document identifier (DI) code functionality; and miscellaneous administrative 

updates as noted in the 830R and 870L change tables. 

c. Procedures: 

(1) Revise DLMS, Volume 2 Chapter 2, as shown in Enclosure 1 to revise section C2.2.4 

and delete section C2.2.5 to eliminate inconsistency between the MILSTRAP and DLMS procedures 

for the FSC/NIIN compatibility check for SPR transactions; 

(2) Revise DLMS, Volume 2 Chapter 3, as shown in Enclosure 2 to incorporate 

administrative updates to the WMR chapter identified in PDC 303.

(3) Revise the MILSTRAP/DLMS Correlation Table, as shown in Enclosure 3. 

(4) Revise DS 870L as follows:

Item 

# 

Location DS 870L Revision 

SPR/LASE Status 

Reason Federal 

IC 

Impact
3 of 16 

ADC 287 

Attachment 

Item 

# 

Location DS 870L Revision 

SPR/LASE Status 

Reason Federal 

IC 

Impact

1. DLMS 

Introductory 

Notes 

Revise DLMS Introductory Note 1:

DLMS Note: 1. Inventory Control Points 

(ICPs) or Integrated Material Managers 

(IMMs) Organizations use this transaction set 

to provide supply Special Program 

Requirements (SPR) status on SPR requests 

(corresponds to MILSTRAP Document 

Identifier (DI) Code DYK functionality). 

The Defense Automatic Addressing System 

Center (DAASC) and Inventory Control Points 

(ICPs) or Integrated Material Managers 

(IMMs) uses this transaction set to notify the 

organization originating the SPR or Logistics 

Asset Support Estimate (LASE) transaction that 

the transaction was rerouted or that the 

Federal Supply Classification (FSC) in the 

original transaction was revised (corresponds 

to MILSTRAP DI Code DZ9 functionality).

ICPs or IMMs use this transaction to notify the 

originator of an SPR or LASE transaction that 

the Federal Supply Classification (FSC) 

provided on the original transaction was

incorrect. 

These changes correct a 

conflict between the 

MILSTRAP LASE/SPR 

procedure for FSC/NIIN 

compatibility edit 

(MILSTRAP Chapter 9 and 

DI Code DZ9) and the 

DLMS procedures and 

870L (DLMS, Vol 2, 

Chapter 2). 

MILSTRAP DI Code DZ9 

corresponds to DS 870L 

when used as a Status 

Notification. 

Per MILSTRAP AP2.1: 

DI Code DZ9 explanation: 

“DAAS notification to the 

submitter that a 

MILSTRAP document was 

rerouted or FSC changed.” 

DS 870L also provides 

functionality of DI Code 

DYK, which has the 

following explanation: 

“ICP status to forecasting 

activity in response to a 

request, follow-up, 

modifier, cancellation, or 

substitute item rejection.” 

No 

revision 

required. 

2. DLMS 

Introductory 

Notes 

Add new DLMS introductory note 4:

4. This revision to the DLMS Supplement 

incorporates Proposed DLMS Changes (PDC) 

and Approved DLMS Changes (ADC) listed. 

PDCs/ADCs listed are available from the 

DLMSO web site http://www.dla.mil/j6/dlmso/eLibrary/changes/processchanges.asp 

- ADC 287, Administrative Update to DLMS 

Supplement 830R (Version 4010), Special 

Program Requirements (SPR), 870L SPR/LASE 

Status, and DLMS Manual (Supply/MILSTRAP)

Identifies DLMS Changes 

included in the DLMS 

Supplement. 

No revision 

required. 
4 of 16 

ADC 287 

Attachment 

Item 

# 

Location DS 870L Revision 

SPR/LASE Status 

Reason Federal 

IC 

Impact

3. 1/BSR01/20 Delete current DLMS note for Status Report 

Code 3, and replace as shown: 

3 Unsolicited Report 

DLMS Note: Use to indicate the DAASC or the 

ICP/IMM is notifying an organization of an 

error in an SPR or LASE transaction.

DLMS Note: Status Notification. DAASC 

uses Status Notification transactions to notify 

the submitter that an SPR or LASE 

transaction was rerouted or that the FSC 

changed. (MILSTRAP DI Code DZ9 

functionality.)

To correct the DS 870L 

purpose stated in the Status 

Report Code to reflect how 

the MILSTRAP 

Administrator understands 

the 870L transaction is 

intended to be used to 

provide Status Notification, 

consistent with MILSTRAP 

guidance for corresponding 

DI Code DZ9. 

Administrative update to 

identify how the Status 

Report Code correlates to 

the corresponding 

MILSTRAP DI Code 

functionality. 

No revision 

required. 

4. 1/BSR01/20 Delete current DLMS note for Status Report 

Code 9 and replace as shown: 

9 Response to a Requirement Forecast 

DLMS Note: Use to indicate the supply source 

is providing planning information related to a 

SPR.

DLMS Note: SPR Status. ICP/IMM uses 

SPR Status transactions to provide SPR status 

to a forecasting activity in response to a DS 

830R SPR transaction. (MILSTRAP DI Code 

DYK functionality.) 

To more clearly identify 

how Status Report Code 9 

is used for SPR Status 

transactions. 

Administrative update to 

identify how the Status 

Report Code correlates to 

the corresponding 

MILSTRAP DI Code 

functionality. 

No revision 

required. 

5. 1/N101/50 Revise Federal Note:

Federal Note: Use any code. 

Administrative update to 

use standard note consistent 

with other DS. 

Revision 

required. 

6. 1/N101/50 Revise DLMS note for GP:

GP Gateway Provider 

DLMS Note: This is DAASC. DAASC uses 

when providing Status Notification that a 

LASE or SPR transaction was rerouted or that 

the FSC has changed (BSR01 Status Report 

Code 3). 

To clearly identify that 

DAASC (gateway provider) 

provides the Status 

Notification transactions 

when SPR (or LASE) 

transaction is rerouted or 

the FSC has changed. 

No revision 

required. 
5 of 16 

ADC 287 

Attachment 

Item 

# 

Location DS 870L Revision 

SPR/LASE Status 

Reason Federal 

IC 

Impact

7. 1/N103/50 

 

Add DLMS enhancement note to qualifiers 1, 9, 

and 10:

2. DLMS enhancement. See introductory 

DLMS note 3a. 

Administrative update to 

identify enhancements with 

standard note consistent 

with other DS.

No revision 

required.

8. 1/N101/50 Revise DLMS note for Z4 to specify SPR 

Status:

Z4 Owning Inventory Control Point 

DLMS Note: Use to identify the ICP or IMM 

providing SPR status (BSR01 Status Report 

Code 9). 

To clarify that SPR status is 

provided, and which 

BSR01 Status Report Code 

is associated with the use of 

qualifier Z4. 

No revision 

required.

9. 1/N101/50 Revise DLMS note for ZN to specify SPR 

Status:

ZN Losing Inventory Manager 

DLMS Note: Use with BSR01 Status Report

Code 9 when the LIM is providing SPR status. 

To clarify that SPR status is 

provided. 

No revision 

required. 

10. 1/N103/50 Add DLMS note 2 to qualifier M4.

M4 DOD Routing Identifier Code (RIC) 

DLMS Notes: 1. The RIC is retained in the 

DLMS to facilitate transaction conversion in a 

mixed DLSS/DLMS environment. Continued 

support of the RIC in a full DLMS environment 

will be assessed at a future date. Typically 

under the DLMS, the RIC will be replaced with 

a DoDAAC or a commercial identifier. 

2. Future streamlined data; see DLMS 

introductory note 3c. 

Administrative update to

add DLMS introductory 

note for RIC for ‘future 

streamlined data’ consistent 

with other DS.

No revision 

required. 

11. 2/REF01/87 Revise Federal Note:

Federal Note: Use any code.

Administrative update to 

use standard note consistent 

with other DS. 

Revision 

required. 

12. 2/REF01/87 Delete Federal note for TN and add a DLMS 

note:

TN Transaction Reference Number 

DLMS Note: Must use to identify the customer 

assigned transaction number (document 

number). 

Administrative update. Revision 

required. 
6 of 16 

ADC 287 

Attachment 

Item 

# 

Location DS 870L Revision 

SPR/LASE Status 

Reason Federal 

IC 

Impact

13. 2/REF01/87 Revise DLMS note for WL:

WL Federal Supply Classification Code 

DLMS Note: Use for ICP Status Notification 

transactions to identify the correct FSC 

associated with the material cited in an SPR or 

LASE transaction. 

To identify transaction 

function (Status 

Notification) that FSC is 

used with. 

No revision 

required. 

14. 2/N101/90 Revise Federal Note:

Federal Note: Use any code. 

Administrative update to 

use standard note consistent 

with other DS. 

Revision 

required. 

15. 2/N103/90 Add DLMS enhancement note to qualifiers 1, 9, 

and 10:

2. DLMS enhancement. See introductory 

DLMS note 3a. 

Administrative update to 

identify enhancements with 

standard note consistent 

with other DS.

No revision 

required.

16. 2/N103/90 Add DLMS note 2 to qualifier M4.

M4 DOD Routing Identifier Code (RIC) 

DLMS Notes: 1. The RIC is retained in the 

DLMS to facilitate transaction conversion in a 

mixed DLSS/DLMS environment. Continued 

support of the RIC in a full DLMS environment 

will be assessed at a future date. Typically 

under the DLMS, the RIC will be replaced with 

a DoDAAC or a commercial identifier. 

2. Future streamlined data; see DLMS 

introductory note 3c. 

Administrative update to 

add DLMS introductory 

note for RIC for ‘future 

streamlined data’ consistent 

with other DS.

No revision 

required. 

17. 2/N101/90 Revise DLMS Note for ZA:

ZA Corrected Address 

DLMS Note: Use to identify the source of 

supply to which DAASC or the ICP or IMM has 

rerouted the transaction.

To correct note to reflect 

that DAASC reroutes SPR 

and LASE transactions 

consistent with MILSTRAP 

and existing SPR 

processing. 

Removes disconnect 

between MILSTRAP and 

DLMS guidance being 

addressed by this PDC. 

No revision 

required. 
7 of 16 

ADC 287 

Attachment 

Item 

# 

Location DS 870L Revision 

SPR/LASE Status 

Reason Federal 

IC 

Impact

18. 2/N101/90 Revise DLMS Note for ZA:

ZA Gaining Inventory Manager 

DLMS Note: Use for SPR Status response 

transactions to identify the Gaining Item 

Manager (GIM) for those items of supply 

involved in logistics reassignment. 

To clearly identify qualifier 

ZA is used with SPR Status 

transactions. 

No revision 

required. 

19. 2/LQ01/145 

and 

2/LQ01/330 

Revise Federal Note:

Federal Note: Use any code. 

Administrative update to 

use standard note consistent 

with other DS. 

Revision 

required. 

20. 2/LQ01/145 Revise DLMS note for qualifier 81:

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 DAASC rerouted 

a LASE or SPR transaction (Status Code BM); 

otherwise do not use. Use with Status 

Notification transactions (BSR01 code 3). 

To clarify when Status 

Code is used with DS 870L. 

The only 2 Status Codes 

that apply to 870L Status 

Notification (and 

corresponding MILSTRAP 

DI Code DZ9) are BG and 

BM 

No revision 

required.

21. 2/LQ01/145 

and 

2/LQ01/330 

Update DLMS notes for qualifier A9:

A9 Supplemental Data 

DLMS Notes: 

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. 

Administrative update for 

consistency with standard 

DLMS notes for qualifier 

A9. 

No revision 

required.
8 of 16 

ADC 287 

Attachment 

Item 

# 

Location DS 870L Revision 

SPR/LASE Status 

Reason Federal 

IC 

Impact

22. 2/LQ01/145 

and 

2/LQ01/330 

Delete qualifier AL and associated Federal and 

DLMS notes:

AL Special Requirements Code

Federal Note:

Use to identify the precedence, special 

handling, and processing requirements.

DLMS Note:

1. Under DLSS, this is carried in the required 

delivery date field.

2. DLMS enhancement; see introductory DLMS 

note 4a.

MILSTRAP Administrator 

believes qualifier ‘AL’ was 

inadvertently added to 

870L. The code relates to 

the Required Delivery Date 

(RDD) in MILS, which is 

not used in the MILSTRAP 

transactions related to 

870L, which are Document 

Identifier Codes DYK and 

DZ9. 

Revision 

required. 

23. 2/LQ01/145 Add qualifier GQ as approved by ADC 77:

GQ Group Qualifier Code 

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. 

Update to incorporate ADC 

77 (Aug 26, 2002) in DS 

870L. 

No revision 

required. 

24. 2/LQ01/145 For qualifiers IMC, MCC, and SMI, delete the 

statement “Indicate NSL for non-stock 

numbered listed items” from the DLMS note.

Administrative update to 

correct DLMS note for 

Navy Item Management 

Code (IMC), Materiel 

Control Code (MCC), and 

Special Materiel 

Identification code (SMIC). 

The statement being deleted 

only applies to the qualifier 

for Navy’s Cognizance 

Symbol (COG). 

No revision 

required.
9 of 16 

ADC 287 

Attachment 

Item 

# 

Location DS 870L Revision 

SPR/LASE Status 

Reason Federal 

IC 

Impact

25. 2/P0106//150 Add Federal note and revise DLMS note:

Federal Note: Use any code.

DLMS Notes: 

DLMS Note: Use only one of codes A1, A2, A4, 

FB, FS, KD, MG, PR, RR, SR, SW, or YP to 

identify the material. Must use the National 

Stock number (NSN) when known except when 

appropriate brand name subsistence items are 

identified by the Subsistence Identification 

Number. 

2. For DLMS use, only the following codes 

are authorized. 

Administrative update to 

use standard notes 

consistent with other DS, 

and to add qualifiers A1 

and MG as noted in item 26 

below. 

Revision 

required. 

26. 2/P0106//150 Add qualifiers A1, MG, and TP with DLMS 

notes:

A1 Plant Equipment Number 

DLMS Notes: 

1. Use to identify plant equipment. 

2. DLMS enhancement. See introductory 

DLMS note 3a. 

MG Manufacturers part number 

DLMS Notes: 

1. Use to identify nonstandard materiel. 

2. DLMS enhancement. See introductory 

DLMS note 3a. 

TP Product Type Code 

DLMS Notes: 

1. For clothing and footwear, use to identify the 

NSN when the material 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. 

To bring the DS 870L 

qualifiers for identifying 

materiel in synch with DS 

830R. 

DS 830R includes 

qualifiers A1, MG, and TP. 

No revision 

required. 
10 of 16 

ADC 287 

Attachment 

Item 

# 

Location DS 870L Revision 

SPR/LASE Status 

Reason Federal 

IC 

Impact

27. 2/P0106/150 Add the following DLMS Note 2 to existing 

qualifiers A2, A4, FB, PR, RR, SR, SW, and YP 

to identify them as DLMS enhancements:

DLMS Note: 2. DLMS enhancement. See 

introductory DLMS note 3a. 

Administrative update to 

identify DLMS 

enhancements. 

No revision 

required. 

28. 2/P0108-

09/150 

Open P0108-09 and add P0108 notes: 

Federal note: Use any code. 

DLMS Notes: 1. When P0106 is qualifier MG, 

must use P0108 qualifier ZB. 

2. For DLMS use, only the following codes are 

authorized. 

To bring the DS 870L 

qualifiers for identifying 

materiel in synch with DS 

830R. 

Revision 

required. 

29. 2/P0108/150 Add qualifier ZB-CAGE code with DLMS note:

ZB Commercial and Government Entity 

(CAGE) 

DLMS Notes: 1. Use with P0106 code MG to 

uniquely identify a manufacturer’s part number. 

2. DLMS enhancement. See introductory 

DLMS note 3a. 

To bring the DS 870L 

qualifiers for identifying 

materiel in synch with DS 

830R. 

Revision 

required. 

(4) Revise DS 830R as follows: 

Item 

# 

Location DS 830R (Version 4010) 

SPR Revision 

Reason Federal 

IC 

Impact

1. DLMS 

Introductory 

Notes 

Revise note 1 to add a second sentence:

DLMS Note: 1. Use a single occurrence of this 

transaction set to transmit SPR transactions to 

one or more ICPs/IMMs. This transaction 

encompasses the functionality of MILSTRAP 

Document Identifier (DI) Codes DYA, DYB, 

DYC, DYD, DYG, DYH, DYJ, DYL, and DYM. 

Administrative update

to identify how the 

corresponding 

MILSTRAP DI Code 

functionality 

incorporated in the DS. 

No revision 

required. 
11 of 16 

ADC 287 

Attachment 

Item 

# 

Location DS 830R (Version 4010) 

SPR Revision 

Reason Federal 

IC 

Impact

2. DLMS 

Introductory 

Notes 

Add new DLMS introductory note 5:

5. This revision to the DLMS Supplement 

incorporates Proposed DLMS Changes (PDC) and 

Approved DLMS Changes (ADC) listed. 

PDCs/ADCs listed are available from the DLMSO 

web site http://www.dla.mil/j6/dlmso/eLibrary/changes/processchanges.asp 

- ADC 287, Administrative Update to DLMS 

Supplement 830R (Version 4010), Special 

Program Requirements (SPR), 870L SPR/LASE 

Status, and DLMS Manual (Supply/MILSTRAP).

- 

Identifies DLMS 

Changes included in the 

DLMS Supplement 

No revision 

required. 

3. 1/N101/230 Revise Federal Note to read:

Federal Note. Use any code. 

Administrative update

for consistency with 

other DS. 

Revision 

required. 

4. 2/BFR13/20 Revise DLMS note for Action Code OT: 

OT Other Unlisted Action 

DLMS Note: Exception Data. Use only with 

2/LIN01/010 codes “A” and “B”. Use only when 

exception data is to be provided. (Associated 

with MILSTRAP DI Code DYB functionality 

when used with LIN01 code “A”. Associated 

with DI Code DYM functionality when used with 

LIN01 code “B”.) 

Administrative update

to identify how the 

information in the DS 

correlates to the 

corresponding 

MILSTRAP DI Code 

functionality. 

No revision 

required. 
12 of 16 

ADC 287 

Attachment 

Item 

# 

Location DS 830R (Version 4010) 

SPR Revision 

Reason Federal 

IC 

Impact

5. 2/LIN01/10 Revise DLMS note as follows: 

DLMS Note: The corresponding MILSTRAP 

DI Code functionality is shown after each code 

for information in a mixed DLSS/DLMS 

environment. 

A - SPR submission request. (DI Code 

DYA/DYB) 

B - SPR Security Assistance (SPR SA) submission

request (DI Code DYL/DYM) 

C - Cancellation of previously submitted SPR 

request. Use indicates cancellation of the entire 

open SPR quantity. (DI Code DYC)

D - Modification of a previously submitted SPR 

(DI Code DYD)

E - Inquiry on status of previously submitted 

SPR (DI Code DYJ)

F - Acceptance of offer to provide substitute 

Material (DI Code DYG)

G - Rejection of offer to provide substitute 

Material (DI Code DYH) 

Administrative update

to clarify transaction 

name (SPR Submission 

vs SPR Request) used 

in DS for consistency 

with corresponding 

procedures, and to 

identify corresponding 

MILSTRAP DI Code 

functionality for 

consistency with other 

MILSTRAP related 

DLMS transactions. 

No revision 

required. 

6. 2/LIN02/10 Revise Federal note and add DLMS notes:

Federal Note: Use any code.

DLMS Notes: 

1. Use only one of codes A1, A2, A4, FB, FS, MG, 

or YP to identify the material. Must use the 

National Stock Number (NSN) (code FS) when 

known, except when appropriate brand name 

subsistence items are identified by the Subsistence 

Identification Number (code A4).

2. For DLMS use, only the following codes are 

authorized. 

Administrative update

to use standard notes 

consistent with other 

DS. 

Revision 

required. 
13 of 16 

ADC 287 

Attachment 

Item 

# 

Location DS 830R (Version 4010) 

SPR Revision 

Reason Federal 

IC 

Impact

7. 2/LIN02/10 Delete DLMS note from qualifier FS. 

FS National Stock Number 

DLMS Note: Must use NSN when known. 

Administrative update

Note is redundant as 

LIN02 level note states 

Must use National 

stock Number when 

known. 

No revision 

required. 

8. 2/LIN04/10 Add Federal and DLMS note:

Federal Note: Use any code.

DLMS Note: For DLMS use, only the following 

codes are authorized.

Administrative update

to use standard notes 

consistent with other 

DS. The DS identifies 

the specific codes that 

can be used. 

Revision 

required. 

9. 2/REF01/140 Revise Federal Note:

Federal Note: Use any code.

Administrative update

to use standard note 

consistent with other 

DS. The DS identifies 

the specific codes that 

can be used. 

Revision 

required. 

10. 2/REF01/140 Add DLMS note to Qualifier TN:

TN Transaction Reference Number 

DLMS Note: This is the document number.

Administrative update No revision 

required. 

11. 2/N101/320 Revise Federal Note:

Federal Note: Use any code.

Administrative update

to use standard note 

consistent with other 

DS. 

Revision 

required. 

12. 2/LQ01/400 

and 

2/LQ01/440 

Revise Federal Note:

Federal Note: Use any code.

Administrative update

to use standard note 

consistent with other 

DS. 

Revision 

required. 
14 of 16 

ADC 287 

Attachment 

Item 

# 

Location DS 830R (Version 4010) 

SPR Revision 

Reason Federal 

IC 

Impact

13. 2/LQ01/400 

and 

2/LQ01/440 

Update DLMS notes for qualifier A9:

A9 Supplemental Data 

DLMS Notes: 

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

3. Expanded use of this field for supplemental 

data without size restriction is a DLMS 

enhancement; see introductory DLMS note 4a. 

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

Administrative update

or consistency with 

standard DLMS notes 

for qualifier A9.

No revision 

required.

14. 2/LQ01/400 

and 

2/LQ01/440 

Delete qualifier AL and associated Federal and 

DLMS notes:

AL Special Requirements Code

Federal Note:

Use to identify the precedence, special handling, 

and processing requirements.

DLMS Note:

1. Under DLSS, this is carried in the required 

delivery date field.

2. DLMS enhancement; see introductory DLMS 

note 4a.

MILSTRAP 

Administrator believes 

qualifier ‘AL’ was 

inadvertently added to 

830R. The code relates 

to the Required 

Delivery Date (RDD) 

in MILS, which is not 

used in the MILSTRAP 

transactions related to 

830R, which are DI 

Codes DYA, DYB, 

DYC, DYD, DYG, 

DYH, DYJ, DYL, and 

DYM. 

Revision 

required. 
15 of 16 

ADC 287 

Attachment 

Item 

# 

Location DS 830R (Version 4010) 

SPR Revision 

Reason Federal 

IC 

Impact

15. 2/LQ01/400 

and 

2/LQ01/440 

Add qualifier GQ as approved by ADC 77:

GQ Group Qualifier Code 

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. 

Administrative update

to incorporate ADC 77 

(Aug 26, 2002) in DS 

830R. 

No revision 

required. 

d. Alternatives: None. 

5. REASON FOR CHANGE: 

 a. Updates DLMS Volume 2 Supply procedures to correct a disconnect with existing Defense 

Logistics Standard System (aka MILS) SPR processing for DAASC routing and IMM processing for 

FSC/NIIN compatibility for SPR transactions. Under MILSTRAP procedures, DAASC checks for 

FSC/NIIN compatibility on SPR transactions and generates DI Code DZ9 Status Notification 

transactions when required. Under the DLMS procedures, the IMM performs this edit and creates the 

Status Notification transaction. The MILSTRAP Administrator believed that DAASC performs the 

edit check and generates the DZ9 (or corresponding 870L) Status Notification transaction in 

accordance with MILSTRAP guidance, and staffed this change to document the correction of the 

disconnect. This change updates DLMS, Volume 2, chapter 2 and DS 870L to reflect this. 

b. Administrative update to DLMS Volume 2, Chapters 2 and 3 to identify MILSTRAP DI Code 

functionality associated with the DLMS SPR and War Materiel Requirements transactions. Provides 

administrative updates to terminology in the DS 830R for consistency with the DLMS/MILSTRAP 

procedural language; and miscellaneous other administrative updates as noted in the DS change tables. 

6. ADVANTAGES and DISADVANTAGES: 

 a. ADVANTAGES: Updates and clarifies DLMS procedures associated with MILSTRAP functions 

for SPR and providing Status Notification. Identifies in the DLMS manual/transactions, the correlation 

between MILSTRAP DI Codes and DLMS transactions. This information is useful in a mixed 

DLSS/DLMS environment. 

 b. DISADVANTAGES: None. 
16 of 16 

ADC 287 

Attachment 

7. IMPACT: 

a. Revisions to DoD 4000.25-M, DLMS, and DS 830R and 870L. 

b. No known system impact. The disconnect being addressed is that MILSTRAP business rules 

have DAASC perform the FSC/NIIN compatibility check for SPR transactions and generate the 

associated DZ9 Status Notification, while the DLMS business rules have the ICP/IMM perform the 

FSC/NIIN compatibility check for SPR transactions, and generate the associated DS 870L Status 

Notification. 

1) PDC 303 requested that the Components that have implemented DLMS for SPR 

assure that their processing reflects existing MILSTRAP business rules logic for SPR FSC/NIIN 

compatibility check being performed by DAASC rather than the ICP/IMM, and that this change will not 

impact their systems. 

2) PDC 303 requested that DAASC verify that they perform the FSC/NIIN check for 

SPR transactions and generates DI Code DZ9 for MILS customers, or corresponding 870L for DLMS 

customers. 

3 Enclosures 
DoD 4000.25-M, Volume 2 

C2-1

ADC 287, Enclosure 1 

DLMS, Vol 2, Chapter 2 

ENCLOSURE 1 TO ADC 287 

Changes are identified by red, bold, italicized, text. 

C2. CHAPTER 2

SPECIAL PROGRAM REQUIREMENTS

AND DEMAND DATA EXCHANGE FORECASTS

C2.1. GENERAL. 

 C2.1.1. Purpose. This chapter provides procedures for Special Program Requirements 

(SPRs) and Demand Data Exchange (DDE) Forecasts 

C2.1.2. Transactions. This chapter addresses the procedures to the following 

ASC X12 transaction functions identified by their beginning segment and report type 

code. Other DLMS formats, such as XML, are also available. See the DLMSO website 

for available DLMS formats: http://www.dla.mil/j6/dlmso/elibrary/TransFormats/140_997.asp. The corresponding Defense Logistics 

Standard Systems (DLSS) MILSTRAP transaction functionality is identified for 

information purposes in a mixed DLSS/DLMS environment. 

 C2.1.2.1. DDE Forecast [This section is not being updated by ADC 287. 

Changes to this section are being staffed by PDC 297] 

 C2.1.2.2. SPR is DS to Federal IC 830R (version 4010) identified by 

beginning segment (1/BFR12/020) Planning Schedule Type Code XA – Requirement 

Forecast. SPR functions are further broken down in 2/LIN01/10 to identify SPR 

Request, SPR Security Assistance Request, SPR Cancellation, SPR Modification, SPR 

Acceptance or Rejection of Substitute Item, and SPR Inquiry. This transaction 

provides MILSTRAP DI Codes DYA, DYB, DYC, DYD, DYG, DYH, DYJ, DYL, and 

DYM functionality. The specific 2/LIN01/10 correlation to the MILSTRAP DI Codes 

is as follows: 

 C2.1.2.2.1. DI Code DYA, SPR Request = LIN01 Code A - SPR Request 

 C2.1.2.2.2. DI Code DYB, SPR Request (Exception Data) = LIN01 

Code A - SPR Request, with BFR13 Action Code OT to indicate exception data is 

provided. 

 C2.1.2.2.3. DI Code DYC, SPR Cancellation = LIN01 Code C - Cancellation. 

 C2.1.2.2.4. DI Code DYD, SPR Modifier = LIN01 Code D - Modification. 

 C2.1.2.2.5. DI Code DYG, SPR Substitute Item Acceptance = LIN01 

Code F- Acceptance of offer to provide substitute. 
DoD 4000.25-M, Volume 2 

C2-2

ADC 287, Enclosure 1 

DLMS, Vol 2, Chapter 2 

 C2.1.2.2.6. DI Code DYH, SPR Substitute Item Rejection = LIN01 

Code G- Rejection of offer to provide substitute. 

 C2.1.2.2.7. DI Code DYJ, SPR Follow-up = LIN01 Code E – Inquiry 

on Status of previously submitted SPR 

 C2.1.2.2.8. DI Code DYL, SPR Request (Cooperative Logistics Supply 

Support Arrangement (CLSSA) = LIN01 Code B – SPR Security Assistance Request. 

 C2.1.2.2.9. DI Code DYM, SPR Request (Exception Data for CLSSA) 

LIN01 Code B – SPR Security Assistance Request, with BFR13 Action Code OT to 

indicate exception data is provided. 

 C2.1.2.3. SPR Status is DS to Federal IC 870L identified by beginning 

segment (1/BSR01/020) Status Report Code 9 – Response to a Requirement Forecast. 

This transaction provides MILSTRAP DI Code DYK functionality. 

 C2.1.2.4. Status Notification is DS to Federal IC 870L identified by 

beginning segment (1/BSR01/020) Status Report Code 3 – Unsolicited Report. This 

transaction provides MILSTRAP DI Code DZ9 functionality. 

 C2.2. SPRs, DS 830R. This section provides procedures for SPRs forecasting for 

items required to support special programs or projects which are of a nonrepetitive nature and 

cannot be forecast by the inventory control point (ICP) based on demand data, and which 

have the greatest probability of materializing and resulting in the eventual submission of 

requisitions. GSA does not participate in the SPR process. 

 C2.2.1. Forecasting activities may submit SPR Requests for requirements meeting 

one or more of the following criteria: 

 C2.2.1.1. One-time training exercises or maneuvers. 

 C2.2.1.2. Repair or rebuild programs that are either nonrecurring or are 

seldom or irregularly programmed. 

 C2.2.1.3. New constructions (ships, buildings, etc.). 

 C2.2.1.4. One-time alterations, modifications, or conversion programs. 

 C2.2.1.5. Initial issue of existing items (i.e., outfittings, activations, and 

changes in authorized allowances). 

 C2.2.1.6. Initial requirements for special operational projects. 

 C2.2.1.7. Requirements for initial testing. 

 C2.2.1.8. Requirements for Government-furnished property. 
DoD 4000.25-M, Volume 2 

C2-3

ADC 287, Enclosure 1 

DLMS, Vol 2, Chapter 2 

 C2.2.1.9. Requirements for infrequently planned support operations such as 

Arctic and Antarctic resupply missions. 

 C2.2.1.10. Special situations of a nonrepetitive nature when required in 

support of authorized Security Assistance Program requirements (e.g., initial pipeline 

stockage requirements in support of approved CLSSA, etc.). 

 C2.2.2. Excluded Requirements. The following types of requirements are excluded 

from identification as SPRs: 

 C2.2.2.1. Provisioning, recurring type. 

 C.2.2.2.2. War Material Requirements. 

 C.2.2.2.3. Requirements for which the DoD Component has a recurring demand. 

 C2.2.2.4. Subsistence, all categories 

 C2.2.3. SPR Submission and Routing 

 C2.2.3.1. Submission Timeframe. The time window for submission of SPRs 

is between 90 calendar days and 5 years prior to the support date (the first day of the 

month in which it is anticipated that material will be requisitioned for the program). 

When procurement is necessary, delivery for an early support date may not be possible 

since the procurement lead time for most items will be greater than 90 calendar days. 

Therefore, forecasting activities should submit SPRs to ICPs as far in advance of the 

support date as practical. 

 C2.2.3.2. Forecasting. Forecasting activities shall prepare an SPR Request 

Transaction to the ICP. When the requirement for an item is such that material will be 

required in phases (e.g., 100 each per month; 100 per quarter, etc.), the forecasting 

activity shall stratify the forecast quantity by the support date as allowed by the DLMS 

transaction. 

C2.2.4. Defense Automatic Addressing System Center (DAASC) Processing for 

SPR. DAASC shall pass or route SPR inquiries as follows:

C2.2.4.1. Correct Source of Supply (SOS). If the transaction is directed to

the correct SOS, DAASC shall pass the transaction to that activity.

C2.2.4.2. Incorrect SOS. If the inquiry is directed to an incorrect SOS, and 

the correct SOS is not the General Services Administration (GSA), DAASC shall reroute 

the transaction to the correct SOS and transmit DS to Federal IC 870L, Special Program 

Requirement (SPR)/ Logistics Asset Support Estimate (LASE) Status, to the submitter 

citing Status Code BM. Recipients of Status Code BM shall update their records to 

reflect the correct SOS.

C2.2.4.3. GSA Directed Transactions. If the inquiry is directed to a correct 

GSA SOS or to an incorrect SOS, but GSA is the correct SOS, DAASC shall reject the 
DoD 4000.25-M, Volume 2 

C2-4

ADC 287, Enclosure 1 

DLMS, Vol 2, Chapter 2 

transaction to the submitter with DS to Federal IC 824, Reject Advice, citing Reject 

Advice Code AX.

C2.2.5. Integrated Material Manager (IMM) Validation and Rejection. IMMs shall 

reject or provide status for SPR inquiries citing the appropriate reject or status code as 

follows:

C.2.2.5.1. Obsolete Items. Reject inquiries received for an obsolete/inactive 

National Stock Number (NSN) that the IMM cannot support with a DS 824. 

C2.2.5.2. Non-Centrally Managed Items. Reject inquiries received for an item 

that is not centrally managed and stocked.

C2.2.5.3. Federal Supply Classification (FSC)/National Item Identification 

Number (NIIN) Compatibility. When the IMM receives an SPR inquiry with an 

incompatible FSC and NIIN, the IMM shall research to determine if the FSC matches a 

previously assigned FSC for the NIIN.

C2.2.5.3.1. Matching FSC. If the submitted FSC matches the previous 

assigned FSC, change the FSC to the current (correct) FSC, continue processing the 

inquiry, and furnish the submitter with a DS 870L status, citing Status Code BG. 

Recipients of Status Code BG shall update their records to reflect the correct FSC.

C2.2.5.3.2. Non-Matching FSC. If the FSC does not match, reject the 

inquiry to the submitter with DS 824 citing Status Code CG.

ADC 287 NOTE – BY THIS ADC SECTIONS C2.2.4. and C2.2.5 ABOVE ARE 

REPLACED WITH THE FOLLOWING 

 C2.2.4. Defense Automatic Addressing System Center (DAASC) Processing for 

SPR Transactions. Upon receipt of the DS 830R SPR transactions, DAASC shall edit 

the National Stock Number (NSN) of the incoming transaction to determine if the 

National Item Identification Number (NIIN) can be identified, if the Federal Supply 

Class (FSC) is compatible with the NIIN, and if the transaction is directed to the 

correct Source of Supply (SOS). DAASC shall pass the transaction, reject the 

transaction, or effect necessary changes to process the transaction and provide 

appropriate status notification or reject transactions to the submitter as follows: 

 C2.2.4.1. If the NIIN is valid (including NIINs coded obsolete/inactive) but 

the FSC and NIIN are not compatible, DAASC shall correct the FSC and provide DS 

870L Status Notification Transaction to the submitter. DAASC shall prepare the 

notification whenever the FSC is corrected in the incoming transaction. Show the 

correct FSC and Status Code BG in the Status Notification Transaction. 

 C2.2.4.2. If the NIIN is valid (including NIINs coded obsolete/inactive), 

screen the SOS file Service record (or IMM record when the Service record source is 
DoD 4000.25-M, Volume 2 

C2-5

ADC 287, Enclosure 1 

DLMS, Vol 2, Chapter 2 

either another DoD Component activity or matches the input transaction "from" 

organization) and process as follows:1

 C2.2.4.2.1. Correct SOS. If the transaction is directed to the correct 

non-GSA SOS, DAASC shall pass the transaction to that activity. 

 C2.2.4.2.2. Incorrect SOS – Reroute. If the inquiry is directed to an 

incorrect SOS, and the correct SOS is not GSA, DAASC shall reroute the transaction to 

the correct SOS and transmit a Status Notification to the submitter citing Status Code 

BM. DAASC shall identify the correct SOS in the notification transaction. 

 C2.2.4.2.3. GSA Directed Transactions. If the inquiry is directed to a 

correct GSA SOS or to an incorrect SOS, but GSA is the correct SOS, DAASC shall 

reject the transaction to the submitter with DS to Federal IC 824R, Reject Advice, citing 

Reject Advice Code AX. 

 C2.2.4.3. If the NIIN cannot be identified, DAASC shall reject the 

transaction to the submitter citing Reject Advice Code AD. 

 C2.2.5. Reject Advice Transactions Recipients. Activities in receipt of DS 824Rs 

shall take appropriate action as indicated by the reject advice code. In addition, 

recipients of Reject Advice Code AB shall advise their designated Component contact 

point for cataloging data of a DAASC SOS file discrepancy. 

 C2.2.6. Status Notification Transaction Recipients. Activities in receipt of Status 

Notification Transactions shall notify other activities requiring knowledge of the 

change and will ensure all future SPR transactions show the change identified by the 

status code in the notification. 

 C2.2.6.1. Recipients of Status Code BG shall update internal SPR records 

to show the correct FSC identified in the notification. The recipient shall review the 

NSN (FSC and NIIN) to ensure the SPR being processed is for the desired item. If the 

NSN is not the desired item, the SPR originator shall submit an SPR Cancellation to 

the SOS. 

 C2.2.6.2. Recipients of Status Code BM shall update their records to show 

the correct SOS. 

 C2.2.7. IMM Processing of SPR Requests

 C2.2.7.1. SOS Risk. The IMM measures the size of the requirement being 

forecasted to determine its acceptability in terms of the risk of long supply being generated. 

This measurement requires consideration of the size of the forecasted quantity in relation to 

the normal demand estimated for the item being forecasted, the value (cost) of this 

quantity, the supply status of the item being forecasted, funding capability of the IMM, 

accuracy of past forecasts, and the degree of assurance that requisitions will follow. 

 

1

 SOS for obsolete/inactive items will be taken from the SOS file when possible; otherwise, 

the SOS will be the activity identified as the TO activity in the incoming transaction. 
DoD 4000.25-M, Volume 2 

C2-6

ADC 287, Enclosure 1 

DLMS, Vol 2, Chapter 2 

 C2.2.7.2. SPR Status Transaction. The IMM shall determine action to be taken 

on the SPR and within 15 calendar days after receipt of the request shall provide 

appropriate status using the SPR Status Transaction. SPR Status Transactions shall advise 

the forecasting activity of acceptance, rejection (other than for correction and 

resubmission), or other action required on the SPR. When an IMM receives an SPR 

Request Transaction that cannot be processed due to erroneous or missing data, the IMM 

shall reject the request, using DS 824R, for correction and resubmission. 

 C2.2.8. Inquiry on SPR Requests. When the forecasting activity has not received a 

SPR Status Transaction or a DS 824R within 21 calendar days from the SPR request

submission date, the forecasting activity may submit an SPR Inquiry Transaction to the 

ICP. 

 C2.2.9. ICP Action on SPR Inquiry

 C2.2.9.1. No Record of Receipt. When there is no record of receipt of the 

original SPR request, the IMM shall process the SPR Inquiry Transaction as an original 

SPR request. 

 C2.2.9.2. Replies to SPRs. IMMs shall prepare replies to SPR inquiries, as 

specified in section C2.2.7 above. 

 C2.2.10. Modification of SPR Requests. The forecasting activity shall send an SPR 

Modification Transaction to submit changes for a previously submitted SPR request to 

replace data in the original request. Submit SPR modifiers only to change the quantity, the 

project code, the coast designator, the support date, the ship-to address, and/or the initiator 

of the SPR requirement. If the originator of the SPR modifier differs from the originator of 

the original SPR, maintain a record of the revised originator. 

 C2.2.11. Response to SPR Modification. The ICP shall prepare replies to SPR 

Modification Transactions, as specified in section C2.2.7, above. 

 C2.2.12. Cancellation of SPR Requests. The forecasting activity may submit an SPR 

Cancellation Transaction for a previously submitted SPR request. Cancellations must be 

for the total quantity applicable to the SPR. 

 C2.2.13. Response to SPR Cancellations. The ICP shall reply to SPR Cancellation 

Transactions with an SPR Status Transaction citing SPR Status Code PD indicating that 

the cancellation was accepted. 

 C2.2.14. Acceptance/Rejection of Substitute Item. Forecasting activities in receipt of 

SPR responses offering a substitute item shall transmit an SPR Acceptance or Rejection of 

Substitute Item Transaction to indicate acceptance or rejection of substitute material. 

 C2.2.15. Response to Substitute Item Rejection. The IMM shall initiate action on the 

item originally requested. The IMM must prepare status responses, as specified in section

C2.2.7, above. 

 C2.2.16. Retention of SPR Requests. The ICP shall retain SPR requests until: 
DoD 4000.25-M, Volume 2 

C2-7

ADC 287, Enclosure 1 

DLMS, Vol 2, Chapter 2 

 C2.2.16.1. The support date of those requirements for which SPR Status Code 

PA was furnished or until a requisition is received that can be identified to all or a portion 

of a particular SPR quantity. 

 C2.2.16.2. One procurement lead time/assembly time away from the support 

date when procurement/assembly is required in support of those requirements for which 

SPR Status Code PB was furnished. 

 C2.2.16.3. Assembly time prior to support date when extra time is required for 

assembly in support of those requirements for which SPR Status Code PC was furnished. 

 C2.2.17. Follow-on Status. The IMM shall provide revised SPR Status Transactions

when the situation changes (e.g., change in procurement lead time, procurement is required 

for material originally anticipated to be available from stock, etc.). Generally, these situation 

changes are unusual in nature, are not programmed for, and require off-line processing. 

IMMs must provide the status, as specified in section C2.2.7, above. 

 C2.2.18. Preparation of SPR Shipments

 C2.2.18.1. Response Timeframe. When an SPR Status Transaction citing 

SPR Status Code PA is received, requisitions citing Demand Code P should be submitted 

for the SPR related requirements in time to allow for delivery within the appropriate time 

standard prescribed by Uniform Material Movement and Issue Priority System (UMMIPS). 

Demand Code P indicates to the ICP that the requisition is for material previously 

forecasted as an SPR. This enables the ICP to control and apply the appropriate logic for 

the demand generated by the requisition. 

 C2.2.18.2. Establishing Audit Trail. Requisitions submitted as a result of an 

SPR shall include the transaction number (document number) from the original SPR to 

establish an audit trail between the SPR and the subsequent requisitions. This audit trail 

provides a means to determine whether follow-on requisitions are submitted for 

requirements forecasted through SPRs. 

 C2.2.18.3. Item Deletion. When an SPR Status Transaction is received citing 

SPR Status Code PR, the SPR is being deleted and the item is a procurement lead 

time/assembly time away from the support date. If the requirement is still valid, the 

requiring activity must immediately submit a DS to Federal IC 511R, Requisition, citing 

Demand Code O. 

 C2.2.19. Logistics Reassignments

 C2.2.19.1. Logistics Loss. When an item is involved in a logistics loss to an 

IMM of another DoD Component, the losing inventory manager (LIM) shall send an SPR

Status Transaction to the forecasting activity containing SPR Status Code PV. This 

status indicates that the item has been involved in a logistics reassignment and a new SPR 

Request Transaction must be submitted to the gaining inventory manager (GIM). 
DoD 4000.25-M, Volume 2 

C2-8

ADC 287, Enclosure 1 

DLMS, Vol 2, Chapter 2 

 C2.2.19.2. Logistics Loss within Same DoD Component. When the logistics 

loss is to an IMM within the same DoD Component, the LIM shall forward the record of 

the SPR Request Transaction to the GIM. No status needs to be furnished the forecasting 

activity. 

=============================================================== 

C2.3. DEMAND DATA EXCHANGE (DDE) FORECASTS, DS 830D. 

ADC NOTE: SECTION C2.3: Changes to section C2.3, DDE Forecasts, are being staffed 

separately by PDC 297, and are not impacted by, nor included in, this ADC. 

===============================================================
DoD 4000.25-M, Volume 2 

C3-1 

ADC 287, Enclosure 2 

ENCLOSURE 2 TO ADC 287 

C3. CHAPTER 3

Changes are identified by red, bold, italicized, text. 

WAR MATERIAL REQUIREMENTS AND 

SIMULATED MOBILIZATION EXERCISES

C3.1. GENERAL. 

C3.1.1. Purpose. This chapter prescribes: 

 C3.1.1.1. Procedures and responsibilities for submission War Material 

Requirements (WMR) to include: 

 C3.1.1.1.1. Submission of WMR data from the DoD Components to the 

IMMs of the Military Departments, DLA, and GSA. 

 C3.1.1.1.2. Edit and validation of WMR data by IMMs and rejection of 

incomplete or invalid input. 

 C3.1.1.1.3. Providing output from the LIM to the GIM upon logistical 

reassignment of a WMR item. 

 C3.1.1.2. Guidelines that affect simulated mobilization exercises. 

C3.1.2. Transactions. This chapter addresses the procedures applicable to DS to 

Federal IC 830W, WMR transaction . The WMR transaction has beginning segment 

(1/BFR12/020) Planning Schedule Type Code XF –War Reserve Forecast. The WMR 

Transaction function is further broken down by the 2/LQ01/190 WMR Code (qualifier 

‘LZ’ ) to provide the functionality of MILSTRAP DI Codes DMA, DMB, DMC, DMD, and 

DME. The specific 2/LQ01/190 WMR Code correlation to the MILSTRAP DI Codes is as 

follows: 

 C3.1.2.1. DI Code DMA, Recurring U.S. Other WMR Data = LQ01 qualifier 

‘LZ’ WMR Code 7 - Recurring U.S. Balance War Reserves. 

 C3.1.2.2. DI Code DMB, Nonrecurring U.S. Other WMR Data = LQ01 

qualifier ‘LZ’ WMR Code 8 - Nonrecurring U.S. Balance War Reserves. 

 C3.1.2.3. DI Code DMC, Nonrecurring Allies Other WMR Data = LQ01 

qualifier ‘LZ’ WMR Code 9 - Nonrecurring Allies Balance War Reserves. 

 C3.1.2.4. DI Code DMD, WMR Forecasted Return Data = LQ01 qualifier 

‘LZ’ WMR Code 4 - WMR Forecasted Reparable Return. 
DoD 4000.25-M, Volume 2 

C3-2 

ADC 287, Enclosure 2 

 C3.1.2.5. DI Code DME, WMR Visibility Data = LQ01 qualifier ‘LZ’ 

WMR Code 10 - Pre-Positioned War Reserve. Wholesale, Protected And Nonprotected. 

C3.2. WMR

 C3.2.1. DoD Policy. DoD policy for management and development of WMR is 

contained in DoD Directive 3110.6. 

 C3.2.2. Data Transmission. The DoD Components shall send DS 830W data to 

reach IMMs by 15 February of each year and will submit corrections and/or changes as 

required. Do not submit zero quantity requirements. 

 C3.2.3. DoD Component Input. The IMM shall control each DoD Component's 

input WMR Transactions, edit the WMR Transaction, and validate the edited 

transactions for adequacy and accuracy of data. The IMM shall consider validated 

requirements in the annual computation of the Balance War Reserve, and in any 

recomputation of these requirements upon receipt of corrected or revised input. When a 

WMR Transaction contains an invalid NSN, unit of issue, quantity or date, process a DS 

to Federal IC 824R, Reject Advice. However, when the transaction is invalid for any 

other reason, manually reject the entire submission to the submitting DoD Component. 

Include all rejects on a listing showing an image of the input transaction and a code 

identifying the reason for the reject. Mail the listing together with a letter explaining the 

reject code and action (s) required by the submitter. 

 C3.2.4. Reassigned Items. When items are logistically reassigned, the LIM shall

send the GIM a listing of WMR data with a supporting WMR Transaction, as prescribed 

in Chapter 9, paragraph C9.4.6. 

C3.3. SIMULATED MOBILIZATION EXERCISES. When establishing plans that 

require simulated mobilization exercises, identify the associated transactions as simulated 

mobilization exercise transactions as provided for in the applicable implementation 

convention. Do not process simulated mobilization transactions in the supply distribution 

system(s) as action documents which affect accountable/unit records. The DoD 

Component activities responsible for initiating these exercises must use extreme caution 

to ensure procedures are explicit and that complete coordination with all participants is 

done. 
1 of 1 

ADC 287, Enclosure 3

MILSTRA/DLMS Correlation Table 

ENCLOSURE 3 TO ADC 287 

Changes are identified by red, bold, italicized, text. 

Update the DLMS to MILSTRAP DI Code Correlation Table to revise 2/LIN01/10 Code A, from 

“SPR Submission” to “SPR Request” for consistency with language used in the DLMS/MILSTRAP 

procedures, and update being made to DS 830R, Version 4010. The cross reference tale is available 

at: http://www.dla.mil/j-6/dlmso/eApplications/LogDataAdmin/dlssdlmscrossreftable.asp

DS # DLMS Supplement Title DI Code(s) DS Accredited Standards Committee (ASC) X12 Functional 

Equivalent to MILSTRAP DI Code 

 Beginning Segment Additional Information needed 

830R Special Program 

Requirements 

DYA 1/BFR12/20 Planning 

Schedule Type Code XA 

– Requirement Forecast 

2/LIN01/10 Code A - SPR 

Submission Request

830R Special Program 

Requirements 

DYB 1/BFR12/20 Planning 

Schedule Type Code XA 

– Requirement Forecast 

With 1/BFR13/20 Action 

Code OT (Exception Data) 

2/LIN01/10 Code A - SPR 

Submission Request

830R Special Program 

Requirements 

DYC 1/BFR12/20 Planning 

Schedule Type Code XA 

– Requirement Forecast 

2/LIN01/10 Code C – Cancellation 

830R Special Program 

Requirements 

DYD 1/BFR12/20 Planning 

Schedule Type Code XA 

– Requirement Forecast 

2/LIN01/10 Code D - Modification 

830R Special Program 

Requirements 

DYG 1/BFR12/20 Planning 

Schedule Type Code XA 

– Requirement Forecast 

2/LIN01/10 Code F – Acceptance 

of offer to provide substitute 

830R Special Program 

Requirements 

DYH 1/BFR12/20 Planning 

Schedule Type Code XA 

– Requirement Forecast 

2/LIN01/10 Code G – Rejection of 

offer to provide substitute 

830R Special Program 

Requirements 

DYJ 1/BFR12/20 Planning 

Schedule Type Code XA 

– Requirement Forecast 

2/LIN01/10 Code E – Inquiry on 

status of previously submitted SPR 

830R Special Program 

Requirements 

DYL 1/BFR12/20 Planning 

Schedule Type Code XA 

– Requirement Forecast 

Requirement Based 

2/LIN01/10 Code B – SPR Security 

Assistance Submission Request

830R Special Program 

Requirements 

DYM 1/BFR12/20 Planning 

Schedule Type Code XA 

– Requirement Forecast 

With 1/BFR13/20 Action 

Code OT (Exception Data) 

2/LIN01/10 Code B – SPR Security 

Assistance Submission Request