DEFENSE LOGISTICS AGENCY

HEADQUARTERS

8725 JOHN J. KINGMAN ROAD, SUITE 2533

FT. BELVOIR, VIRGINIA 22060-622 1

IN REPLY

REFER TO DLMSO

MEMORANDUM FOR: SUPPLY PRC MEMBERS

SUBJECT: Approved DLMS Change 93, Inclusion of Status Code BP in Material

Obligation Validation (MOV) Procedures (Supply/MILSTRIP)

This attached change to DOD 4000.25-1-M, Military Standard Requisitioning and Issue

Procedures (MILSTRIP), and DOD 4000.25-M, Defense Logistics Management System

(DLMS), is approved for staggered implementation. Components may defer associated

automated processing pending logistics systems modernization. Components should identify

implementation dates to DLMSO. DLA has reported that this process is implemented under

legacy systems and will perpetuate under modernization.

Addressees may direct questions to the DLMSO points of contact, Ms. Ellen Hilert,

Chair, Supply Process Review Committee, 703-767-0676, DSN 427-0676, or e-mail:

ellen.hilert@dla.mil or Ms. Vermella Savige, DOD MILSTRIP System Administrator,

703-767-0674, DSN 427-0674, or e-mail: vermella.savage@dla.mil. Others must contact

their Component designated representative.

;:!z&!fI

Standards Office

Attachment

&JSD(L)SCI

LMI
Approved DLMS Change 93

Inclusion of Status Code BP in MOV Procedures

1. ORIGINATOR: 

a. Service/Agency: DLA

b. Sponsor: Ms. Ellen Hilert, Chair, Supply Process Review Committee, 703-767-0676, 

DSN 427-0676, or e-mail: ellen_hilert@hq.dla.mil

2. FUNCTIONAL AREA: Supply

3. REQUESTED CHANGE:

a. Title: Inclusion of Status Code BP in MOV Procedures

b. Description of Change: This change corrects documented procedures for MOV 

to include Status Code BP. 

c. Procedures: Revise MILSTRIP as follows:

C7.1.1.2. A materiel obligation is herein defined as that unfilled portion of a requisition (for 

a stocked or nonstocked item) that is not immediately available for issue but is recorded as a 

commitment for future issue, either by direct delivery from vendor or backordered from 

stock. This includes both NSN and non-NSN items. Accordingly, MOV will pertain to 

those requisitioned items assigned Status Codes BB, BC, BD, BP1, BV, and BZ, as 

applicable. 

_____________________________

1

 Status Code BP may be deferred for inclusion under logistics system modernization.

4. REASON FOR CHANGE: 

a. Status Code BP was developed for use with extended (or deferred) required delivery 

date (RDD) procedures (Codes X and S) subsequent to the documentation for MOV

procedures. Prior to the change that developed Status Code BP, deferred requisitions were 

placed in BB status and validated as part of MOV. In an apparent oversight, the list of status 

code values applicable to MOV was not updated to include Status Code BP. However, 

DLA, under legacy system processing, did incorporate BP status under MOV with no 

problems identified by the Components. It is the intention of DLA to perpetuate inclusion 

of BP status under MOV during modernization. This change is provided to correct the 

administrative error and allow for phased implementation if Components do not currently 

include deferred requisitions in their MOV processing.

b. For ease of review the following information is provided:
MILSTRIP Status Code BB: Item is back ordered against a due-in to stock. The ESD for 

release of materiel to the customer is contained in rp 70-73.

MILSTRIP Status Code BP: Requisition has been deferred per customer instructions. The 

ESD is in rp 70-73.

Extended RDD Code X: Customer enters number of months in rp 63-64 preceded by an X 

in rp 62. The use of extended RDD Code X does not preclude earlier delivery if material is 

available; however, supply sources deferring support provide BP status.

Extended RDD Code S: Customer enters number of months in rp 63-64 preceded by an S 

in rp 62. The use of extended RDD Code S indicates the customer’s desire that material not 

be released prior to 50 days before expiration of the extended RDD. The supply source will 

not ship earlier even if material is available.

5. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Advances the objective of consistent processing across Components 

and clarifies specific business rules. 

b. Disadvantages: None known.

6. IMPACT:

 Publication: MILSTRIP and DLMS; Component implementing procedures.