1 of 6 

 ADC 400, Att 

ATTACHMENT TO ADC 400

Elimination of the DLMS-MILSTRAP Logistics Asset Support Estimate (LASE) Process no 

Longer Required by the DOD Components (DLMS/MILSTRAP/MILSTRIP) 

(staffed by PDC 400 as a follow on to PDC 301A)) 

1. ORIGINATOR: 

a. Service/Agency: Army, HQAMC; DLA J336 

b. Originators: 

(1) HQAMC (Commercial 703-806-8311), Supply Chain Execution Business Team Lead 

(Commercial 256-876-1724), Supply Management Business Area Lead (Commercial 256-313-4250) 

(2) DLA, DLA-J336, DSN 427-4337, COMM 703-767-4337 

(3) Sponsored by: DOD MILSTRAP Administrator, DLA Logistics Management 

Standards, email: Mary.Jane.Johnson@dla.mil 

2. FUNCTIONAL AREA: Supply 

3. REFERENCES: 

a. DLMSO memorandum, May 29, 2008, subject: Proposed DLM Change (PDC) 301, 

Alternative to LASE Process for DLA Managed Assets Using DOD EMALL Supportability 

Analysis Stock Out Report Tool (Supply/MILSTRAP) 

b. DLMSO memorandum, March 25, 2010, subject: PDC 400, Exclude Army from using the 

Logistics Asset Support Estimate (LASE) Process 

c. DLMSO memorandum, November 25, 2009, DLMS Supply Process Review Committee 

Meeting 07-02, October 9-11, 2007, available at www.dla.mil/j-6/dlmso/Archives/archives_sprc.asp 

d. DLMSO memorandum, November 6, 2007, DLMS Supply Process Review Committee 

Meeting 09-01, October 28-29, 2009, available at www.dla.mil/j-6/dlmso/Archives/archives_sprc.asp

e. DOD Instruction (DODI) 4140.01, December 14, 2011, DoD Supply Chain Materiel 

Management Policy, available at www.dtic.mil/whs/directives/corres/pdf/414001p.pdf 

f. DLMSO memorandum, August 5, 2009, subject: Approved DLMS Change (ADC) 333, 

subject: Revision to DLMS, Volume 2, Chapter for logistics Asset Support Estimate (LASE); and 

Administrative Updates to DLMS 846L, 870L, LASE Request Codes and Reject Advice Codes 
2 of 6 

ADC 400, Att 

4. REQUESTED CHANGE: 

a. Brief Overview of Change: This change eliminates the DLMS-MILSTRAP LASE process 

as recommended by the DOD Components after staffing two separate PDCs from DLA and Army 

(DLA PDC 301 (reference 3.a.) and Army PDC 400 (reference 3.b.). The PDCs documented that 

DLA and Army were not implementing LASE in their respective enterprise resource planning 

(ERP) systems: DLA Enterprise Business System (EBS) and Army Logistics Modernization 

Program (LMP). The remaining DOD Components agreed to DLA and Army’s elimination of the 

LASE process. In response to the PDCs, Navy and Air Force stated they would not implement 

LASE in their ERPs, and Marine Corps also concurred with the elimination of LASE.

b. LASE Background: LASE was the MILSTRAP/DLMS procedure for the DOD 

Components to obtain general estimates of the type of supply support that may be anticipated for 

a weapons system. The Components could use LASE transaction to inquire to Integrated 

Materiel Managers (IMMs) about specific NSNs, and the automated replies provided general 

estimates of the type of supply support that could be anticipated. 

c. Description of Change: This change eliminates the MILSTRAP/DLMS LASE process 

(procedures, transaction, and LASE specific codes). This change updates the DOD 4000.25-M 

(DLMS), DOD 4000.25-1-M (MILSTRIP), and DOD 4000.25-2-M (MILSTRAP), manuals to 

eliminate the LASE procedures and associated transactions/codes. LASE is being eliminated 

based on the DOD Component recommendations provided in response to PDC 400. 

5. REASON FOR CHANGE: 

a. DLA documented by PDC 301 that they did not implement LASE in the DLA Enterprise 

Business System (EBS). DLA offered the Services the alternative of using the DOD EMALL 

Supportability Analysis Stock Out Report Tool to obtain information on DLA managed assets. 

All Components concurred with PDC 301; however DLA Logistics Management Standards 

office held the ADC in abeyance due to Army’s indication that they also no longer saw a need 

for LASE. Prior to documentation in PDC 301, the DLA alternative to LASE was discussed at 

Supply PRC Meeting 07-02, October 9-11, 2007 (reference 3.c.)

b. At the Supply PRC Meeting 09-01 (reference 3.d.) Army addressed that they did not plan 

to provide for LASE under Army’s modernized system, LMP. Army would not provide the 

ability for customers to submit LASE transactions to Army; Army would not generate LASE 

transactions to other Components; nor would Army use LASE on an intra-Army basis. The 

MILSTRAP Administrator noted that since LASE is a DOD requirement documented in 

MILSTRAP/DLMS, Army could not unilaterally stop supporting a DOD requirement. She 

further noted that if Army’s modernized system would not support LASE, Army needed to 

submit a PDC to request elimination of the DOD process or provide an Army alternative process. 

In response Army submitted PDC 400. 

c. By PDC 400 the Army documented that they had not used the LASE requirement since 

2007. Army advised they would not pursue funding to support an ERP LASE requirement in LMP 

since LASE had been inactive and no Services had expressed concern over the absence of Army 

participation in LASE. Army was not offering an alternative to LASE, but instead requested its 
3 of 6 

ADC 400, Att 

use with Army be discontinued. As part of staffing PDC 400, DLA logistics Management 

Standards requested that if the Navy, Air Force, Marine Corps, and Coast Guard concurred with 

elimination of LASE for Army, as part of their response to the PDC they also: 

(1) Provide a position on whether they would continue LASE process among Navy, Air 

Force, Marine Corps and Coast Guard, since they would be the only remaining stakeholders in the 

process. 

(2) Provide a position on whether they recommended elimination of the LASE process 

As noted in the PDC 400 Response Table Army, Navy, Air Force, and Marine Corps 

recommended elimination of the LASE process. 

6. REVISIONS TO DOD 4000.25 SERIES OF MANUALS will be documented in the 

MILSTRAP, MILSTRIP and DLMS manuals as follows. Note that the DOD 4000.25 series of 

manuals will be reissued as Defense Logistics Manuals in June 2012, as required by DODI 4140.01 

(reference 3.e.): 

a. DOD 4000.25-M, DLMS: 

(1) DLMS, Volume 2, Chapter 24, LASE. Revise Volume 2, as revised by ADC 333 

(reference 3.f.), to delete Chapter 24, LASE; renumber the remaining chapters; and update the Table 

of Contents as needed.

(2) DLMS Acronyms. Revise to delete LASE. 

(3) DLMS Definitions and Terms. Revise to delete LASE. 

(4) DLMS Data Dictionary. Revise as follows: 

 Note that DLMS 846L LASE transaction and MILSTRAP Document 

Identifier Codes (DICs) DTA, DTB, DTC, and DTD have been cancelled by ADC 400; 

 DLMS 870L is renamed to remove LASE from the title. The DLMS 870L 

name is changed from “Special Program Requirements (SPR) Status; or SPR/Logistics Asset Support 

Estimate (LASE) Notification” to “Special Program Requirements (SPR) Status or Notification”.

 Update DLMS/DLSS cross references as needed. 

 Delete the LASE Request Codes, Data Element ID 1270 Qualifier EU-Request 

Code. 

 Revise the MILSTRIP Status Codes, Data Element 1270 Qualifier 81, code 

value CJ, as noted in subparagraph 6.b. below. 

 Revise MILSTRAP Reject Advice Codes, Data Element ID 1270 Qualifier ETReject Advice Code, as noted in subparagraph 6.c.(5) below. 

(5) Cancel DLMS 846L, LASE transaction and remove from the DLMS website. 
4 of 6 

ADC 400, Att 

(6) Revise DLMS 870L, as shown in Enclosure 2.

b. DOD 4000.25-1-M, MILSTRIP. Revise MILSTRIP Appendix AP 2.16, Status Codes (and 

corresponding DLMS Data Dictionary 1270 qualifier 81), Status Code CJ, to delete explanation 

entry (4) as follows (changes are identified by bold, red italic strikethroughs):

MILSTRIP 

STATUS CODE 

EXPLANATION 

CJ Rejected. 

(1) Item coded (or being coded) "obsolete" or "inactivated." Item in stock number 

field, if different from item requisitioned, can be furnished as a substitute. Unit price 

of the substitute item is in rp 74-80. 

(2) If offered substitute is desired, submit a new requisition1

 with substitute item 

stock number. If only original item is desired, submit a new requisition2

 for 

procurement on DD Form 1348-6. SF 344 may be submitted by authorized activities. 

(See appendix A.) Cite Advice Code 2B. 

(3) Furnish technical data; for example, end item usage, component, make, model, 

series, serial number, drawing piece and/or part number, manual reference, or 

applicable publication. 

(4) Rejected. DoD MILSTRAP DTA Asset Support Request submitted for 

obsolete/inactive NSN, which cannot be supported. (Applies to MILSTRAP DZG 

transaction rejects only.) 

c. DOD 4000.25-2-M, MILSTRAP: 

 (1) MILSTRAP Chapter 14. Delete Chapter 14, LASE; renumber Chapter 15 as Chapter 14; 

update the Table of Contents as needed; 

 (2) MILSTRAP Chapter 9. Revise Chapter 9, Rejection, Routing, and Reversal of 

Transactions, Section C9.3. Routing of Transactions, as shown in Enclosure 1. 

 (3) MILSTRAP Acronyms. Revise to delete LASE. 

 (4) MILSTRAP Definitions and Terms. Revise to delete LASE. 

(5) MILSTRAP Appendix AP 2.8, Reject Advice Codes (and corresponding DLMS Data 

Dictionary 1270 qualifier ET). Revise as follows (changes are identified by bold, red italics and 

strikethroughs): 

CODE EXPLANATION 

AT Reserved for DoD assignment. Rejected. Logistics Asset Support Estimate (LASE) request 

code invalid or blank. 

AU Reserved for DoD assignment. Rejected. LASE request is for an item not centrally managed 

and stocked (Acquisition Advice Codes F, L, P, or W).
5 of 6 

ADC 400, Att 

CODE EXPLANATION 

AV Rejected. Activity identified in record positions 30-35 (DoDAAC) and/or 27-29 (RI code 

(From)) is not authorized to submit LASE transactions. Activity identified in Location 

Reconciliation Request record positions 67-69 (RIC (From)) not valid.

AX Rejected. GSA is SOS for requested LASE or SPR. GSA does not participate in MILSTRAP 

LASE and SPR procedures. If required, submit funded DoD MILSTRIP requisition citing 

applicable required delivery date. 

 

(6) MILSTRAP Appendix 2.14 (AP 2.14), LASE Request Codes (DLMS Data Dictionary 

qualifier EU). Delete AP2.14 LASE Request Codes and renumber remaining appendices as needed; 

update the Table of Contents as needed.

(7) MILSTRAP LASE Transaction Appendices 3.38-3.41. Delete the following 

appendices; renumber remaining appendices as needed; update the Table of Contents as needed: 

 AP3.38, DIC DTA, Asset Support Request. 

 AP3.39, DIC DTB, Asset Support Reply (Asset Data). 

 AP3.40, DIC DTC, Asset Support Reply (Backorder Condition). 

 AP3.41, DIC DTD, Asset Support Request Follow-up. 

7. ADVANTAGES AND DISADVANTAGES: 

a. Advantages. Cost avoidance by not programming an old legacy process into the modernized 

system. 

b. Disadvantages. None identified. 

8. IMPLEMENTATION: Elimination of the LASE process is effective with publication of this 

change, and will be documented in the MILSTRAP, MILSTRIP and DLMS manuals when they are 

reissued as Defense Logistics Manuals in June 2012. 

9. IMPACT: 

a. DOD Components Automated Information System (AIS): 

(1) Army identified no Army impact. Army stated by PDC 400 that Army has not used 

the LASE process for years and no Services have expressed an impact since the Army fielded their 

Logistics Modernization Program (LMP) to the U.S. Army Communications and Electronics 

Command in July 2003 and to the US Army Aviation and Missile Command in May 2009. LMP 

does not process LASE transactions. 

(2) DLA. There would be no impact to DLA. DLA previously documented by PDC 301 

that they did not implement LASE in their modernized system, EBS. 

(3) Air Force, Navy, Marine Corps, and Coast Guard: May require change to AIS 

processing LASE transactions, to stop sending LASE transactions. Each Service should address this 

within their systems as needed. 
6 of 6 

ADC 400, Att 

b. DLMS Data: Refer to paragraph 6, Revisions to DOD 4000.25 series of manuals, for the 

impacts to DLMS Data. 

c. DLA Transaction Services. 

 (1) Defense Automatic Addressing System (DAAS) Publication. May require revision to 

the DAAS manual to revise any guidance associated with the MILSTRAP-DLMS LASE process. 

Draft Defense Logistics Manual (DLM) 4000.25-4 is under development to replace the DOD 

4000.25-10-M, DAAS manual, in accordance with DODI 4140.01. 

(2) DAAS. DLA Logistics Management Standards requested that DLA Transaction Services 

determine if LASE transactions (DICs DTA, DTB, DTC, DTD or 846L) were currently being 

submitted to DAAS. DLA Transaction Services reported that no LASE transactions processed 

through DAAS in March 2012. 

10. RESPONSES TO PDC 400: 

COMPONENT RESPONSE 

USA 

4/27/2010 

Concur. 

USN 

4/19/2010 

Concur. The Navy's position is that we recommend elimination of the LASE 

process. We have not found any interest in this process within Navy, and we do 

not plan to continue this process with Navy ERP. 

USAF 

5/3/2010 

The Air Force concurs with PDC. We agree with the Army and Navy position 

that we eliminate the LASE process. In fact, the Air Force does not plan to 

continue this process with Air Force ERP. 

USMC 

9/23/2010 

This Headquarters has reviewed the impact of the cancellation of LASE to 

Marine Corps and concurs with cancellation of LASE. 

DLA 

4/23/2010 

DLA concurs. 

DPAP 

Contractor 

Support 

3/31/2010 

Do not see any impact to WAWF, GFP CONOPS, IUID Registry, GFP Hub, or 

IUID Policy 

USTRANSCOM 

3/25/2010 

Abstains 

Enclosures 

As stated
1 of 3 

 ADC 400 

 Enclosure 1

ENCLOSURE 1 TO ADC 400 

Elimination of the DLMS-MILSTRAP Logistics Asset Support Estimate (LASE) Process no Longer 

Required by the DOD Components (DLMS/MILSTRAP/MILSTRIP) 

Revise DOD 4000.25-2-M, MILSTRAP, Chapter 9, Rejection, Routing, and Reversal of 

Transactions, Section C9.3., Routing of Transactions, as follows (changes are identified by bold, 

red italic strikethroughs): 

C9.3. ROUTING OF TRANSACTIONS 

 C9.3.1. Submission of MILSTRAP Transactions via the DLA Transaction 

Services. Whenever the submitter has access to the Defense Information Systems 

Network (DISN)/Non-Secure Internet Protocol Router Network (NIPRNET), the following 

MILSTRAP Logistics Asset Support Estimate (LASE) and Special Program 

Requirements (SPR) transactions shall be submitted by DISN/NIPRNET via the DLA 

Transaction Services for routing to the source of supply (SOS): 

CODE DOCUMENT TITLE 

DTA Asset Support Request 

DTD Asset Support Request Follow-Up 

DYA Special Program Requirement Request 

DYC Special Program Requirement Request Cancellation 

DYD Special Program Requirement Request Modifier 

DYG Special Program Requirement Request Substitute Item Acceptance 

DYH Special Program Requirement Request Substitute Item Rejection 

DYJ Special Program Requirement Follow-Up 

DYL Special Program Requirement Request (Cooperative Logistics Supply 

Support Arrangement) 

C9.3.2. DLA Transaction Services Processing for LASE and SPR Transactions. 

Upon receipt of the LASE and SPR transactions identified in C9.3.1, DLA Transaction 

Services shall edit the national stock number (NSN) field of the incoming transactions. 

This edit will 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 SOS. The DLA Transaction Services shall pass the transaction, 

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

appropriate status notification to the submitter as follows: 

 C9.3.2.1. If the NIIN is valid (including NIINs coded obsolete/inactive) but the 

FSC and NIIN are not compatible, correct the FSC and provide NSN change status 

notification to the submitter as prescribed in paragraph C9.3.3., below. 

 C9.3.2.2. If the NIIN is valid (including NIINs coded obsolete/inactive), screen the 

SOS file Service record (or Integrated Materiel Manager record when the Service record 
2 of 3 

 ADC 400, 

 Encl 1

source is either another DoD Component activity or matches the input transaction RI "from") 

and process as follows:1

 C9.3.2.2.1. If the incoming transaction is directed to a correct non-GSA SOS, 

pass the transaction to the activity indicated in record positions 4-6. 

 C9.3.2.2.2. If the incoming transaction is directed to an incorrect SOS and 

the correct SOS is not GSA, provide reroute status notification to the submitter as prescribed 

in paragraph C9.3.3. and reroute the transaction to the correct SOS. 

 C9.3.2.2.3. If the incoming transaction is directed to a correct GSA SOS or to an 

incorrect SOS but the correct SOS is GSA, reject the transaction to the submitter as 

prescribed in paragraph C9.2.3., citing Reject Advice Code AX in record positions 79-80. 

 C9.3.2.3. If the NIIN cannot be identified, reject the transaction to the submitter as 

prescribed in paragraph C9.2.3. citing Reject Advice Code AD in record positions 79-80. 

 C9.3.3. DLA Transaction Services Preparation of Status Notifications. The DLA 

Transaction Services shall prepare and transmit appropriate DI Code DZ9 Status 

Notification(s) (see appendix AP3.55) to the submitter based on the action(s) taken. 

 C9.3.3.1. Prepare a status notification whenever the FSC is corrected in the 

incoming transaction. Reflect the correct FSC in record positions 8-11 and MILSTRIP Status 

Code BG in record positions 79-80. 

 C9.3.3.2. Prepare a status notification whenever the incoming transaction was 

rerouted. Reflect the RI code of the correct SOS in record positions 67-69 and MILSTRIP 

Status Code BM in record positions 79-80. 

 C9.3.3.3. Whenever a status notification is prepared, enter the DI code of the 

incoming transaction in record positions 57-59 of the status notification. 

C9.3.4. Processing Status Notifications and Transaction Rejects by Recipients 

 C9.3.4.1. When MILSTRAP DI Code DZ9 Status Notifications with MILSTRIP 

Status Code BM are received on MILSTRAP transactions, the recipient shall update internal 

LASE/SPR records to reflect the SOS RI code entered in record positions 67-69 of the status 

notification. 

 C9.3.4.2. When DI Code DZ9 MILSTRAP Status Notifications with MILSTRIP 

Status Code BG are received on MILSTRAP transactions, the recipient shall update internal 

LASE/SPR records to reflect the FSC entered in record positions 8-11 of the notification. If 

the status notification is for an SPR transaction, the originator 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 originator will submit an SPR cancellation, DI Code DYC, to the SOS. 

 1

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

identified by the RI code in record positions 4-6 of the incoming transaction. 
3 of 3 

 ADC 400, 

 Encl 1

 C9.3.4.3. DI Code DZG Transaction Rejects will be processed under paragraph 

C9.2.3., above. However, recipients of code AB transaction rejects for LASE and SPR 

documents shall advise their designated Component contact point for cataloging data of a 

DLA Transaction Services SOS file discrepancy. If the LASE/SPR requirement still exists, 

requestors must submit a new LASE/SPR document directly to the correct SOS, bypassing 

the DLA Transaction Services. 

 C9.3.4.4. Recipients of a MILSTRAP status notification shall notify other activities 

requiring knowledge of the change and will ensure all future transactions submitted for the 

document number reflect the change identified by the MILSTRIP status code in the 

notification. 
1 of 3 

 ADC 400 

 Enclosure 2

ENCLOSURE 2 TO ADC 400 

Elimination of the MILSTRAP-DLMS LASE Process and Transactions No Longer Required 

by the DOD Components 

DLMS SUPPLEMENT 870L CHANGE TABLE 

Revise DLMS 870L to eliminate reference to the LASE process as follows: 

# Location DLMS 870L 

Special Program Requirements (SPR) Status or Notification 

Reason 

1. DLMS 

Supplement 

TITLE 

Revise DS 870L Title as follows: 

Old Title: Special Program Requirements (SPR) Status; or 

SPR / Logistics Asset Support Estimate (LASE) Notification 

New Title: 

Special Program Requirements (SPR) Status or Notification 

Eliminates reference to 

the LASE process. 

2. DLMS 

Introductory 

Note 1 

Revise DLMS Note 1 as follows: 

1. Inventory Control Points (ICPs) or Integrated Material 

Managers (IMMs) use this transaction set to provide Special 

Program Requirements (SPR) status on SPR requests 

(corresponds to MILSTRAP Document Identifier (DI) Code 

DYK functionality). The Defense Automatic Addressing 

System Center (DAASC) DLA Transaction Services 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).

Eliminates reference to 

the LASE process. 

3. DLMS 

Introductory 

Note 4 

Add ADC 400 to DLMS introductory note 4: 

- ADC 400, Elimination of the DLMS-MILSTRAP Logistics 

Asset Support Estimate (LASE) Process no Longer Required 

by the DOD Components (DLMS/MILSTRAP/MILSTRIP). 

Identifies PDCs/ADCs 

in the DLMS 

Supplement. 

4. 1/BSR01/20 Revise DLMS Note for qualifier 3 as follows: 

3 Unsolicited Report 

DLMS Note: 

Status Notification. DAASC DLA Transaction Services uses 

Status Notification transactions to notify the submitter that an 

SPR or LASE transaction was rerouted or that the FSC 

changed. (MILSTRAP DIC DZ9 functionality.)

Eliminates reference to 

the LASE process.

NOTE: Administrative 

updates made 

throughout DS 870L to 

change DAASC to DLA 

Transaction Services. 

Those administrative 

updates are not shown in 

this table, unless some 

other change was made 

to the DLMS note. 
2 of 3 

 ADC 400, 

 Encl 2 

# Location DLMS 870L 

Special Program Requirements (SPR) Status or Notification 

Reason 

5. 1/N101/50 Revise DLMS Note for Qualifier GP as follows: 

GP Gateway Provider 

DLMS Note: 

This is DLA Transaction Services DAASC. DAASC DLA 

Transaction Services uses when providing Status Notification 

that a LASE or an SPR transaction was 

rerouted or that the FSC has changed (BSR01 Status Report 

Code 3.)

Eliminates reference to 

the LASE process.

6. 2/HL/10 Revise segment level DLMS note as follows: 

DLMS Note: 

The transaction set hierarchical data structure is for SPR or 

LASE transaction status only.

Eliminates reference to 

the LASE process.

7. 2/HL03/10 Revise DLMS Note for qualifier W as follows: 

W Transaction Reference Number 

DLMS Note: 

Use to identify the individual SPR or LASE transaction status 

loops.

Eliminates reference to 

the LASE process.

8. 2/DTM/80 Revise segment level DLMS note as follows: 

DLMS Note: 

Use in SPR/LASE status transactions.

Eliminates reference to 

the LASE process.

9. 2/REF01/87 Revise DLMS Note for qualifier WL as follows: 

WL Federal Supply Classification Code 

DLMS Note: 

Use for Status Notification transactions to identify the correct 

FSC associated with the materiel cited in 

an SPR or LASE transaction.

Eliminates reference to 

the LASE process. 

10. 2/N101/90 Revise DLMS Note for qualifier 78 as follows: 

78 Service Requester 

DLMS Note: 

Must use to indicate the activity submitting the original SPR 

or LASE transaction.

Eliminates reference to 

the LASE process. 
3 of 3 

 ADC 400, 

 Encl 2 

# Location DLMS 870L 

Special Program Requirements (SPR) Status or Notification 

Reason 

11. 2/LQ01/145 Revise DLMS Note for qualifier 81 as follows: 

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 DLA 

Transaction Services rerouted a LASE or an SPR 

transaction (Status 

Code BM); otherwise do not use. Use with Status Notification 

transactions (BSR01 code 3).

Eliminates reference to 

the LASE process. 

12. 2/QTY/230 Revise segment level DLMS note 2 as follows: 

DLMS Note: 

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

LASE transactions.

Eliminates reference to 

the LASE process. 

13. 2/DTM/240 Revise segment level DLMS note 2 as follows: 

DLMS Note: 

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

LASE transactions.

Eliminates reference to 

the LASE process.