2

DISTRIBUTION:

J4

Supply PRC Members:

USA AMCLG-SM/ATCL SAL DLA DLSC LS/LD

USN NAVSUP 4113B/NAVICP M0417 GSA FCSI

USAF AFMC/LGIA DAASC DSDC SSL

CMC LPS-1 DTRA FCOSCM

DSCA MEAN AP FAA AFZ-500

USCG G-SL NIMA ST D 101

NSA S711 ADUSD(L)SCI

USTRANSCOM TCJ4-LTS

cc:

LMI
Approved DLMS Change 19

DAASC Requisition Edit for OSD/CJCS Invalid/Expired Project Codes

 1. Originator:

a. Service/Agency: USAF

b. Originator: HQ AFMC/LGIA

2. Functional Area: Supply

3. Requested Change:

a. Title: Defense Automated Addressing Systems Center (DAASC) Requisition Edit for 

Office of the Secretary of Defense/Combined Joint Chiefs of Staff (OSD/CJCS) Invalid/Expired 

Project Codes.

b. Description of Change: DoD policy directs that customers determine and 

communicate relative precedence of materiel requirements by application of priority designators, 

required delivery dates, and approved OSD/CJCS Category D project codes. However, there is 

currently no mechanism in place in the requisition process to validate approved OSD/CJCS 

project codes. This proposal establishes procedures for a central DAASC edit for invalid/expired 

project codes. Under this procedure DAASC will blank out invalid/expired project codes and 

continue processing. The customer will be notified of this action via MILSTRIP supply status 

transaction.

c. Procedures: 

a. Short-term.

(1) Revise DoD 4000.25-1-M, Appendix B13, Project Codes, as follows:

(a) Modify paragraph C.4.d(3): 

"(3) Dissemination - Initial dissemination of category D project codes will be accomplished in 

three phase, as follows :

(a) OSD/CJCS letter or message to S/A Headquarters, to the DoD MILSTRIP System 

Administrator, and to the DAASC."

(b) Add new paragraph C.4.d(4):

"(4) Validation - The DAASC will edit all requisitions (DI AM_, AO_, AT_, and APR) for 

invalid/expired OSD/CJCS Category D project codes. If an invalid/expired code is present, 

DAASC will blank the project code, forward the requisition for processing, and report this 

action back to the requisitioner in an AE9 transaction with BK status. To accomplish this, the 

DAASC will establish and maintain an edit table based upon OSD/CJCS letter or message 

(quarterly or as needed) or communication from the MILSTRIP Administrator identifying 

additions/deletions/corrections to project code information. 
2

(2) Revise DoD 4000.25-1-M, Appendix B16, Status Codes, as follows: 

CODE EXPLANATION

"BK Requisition data elements have been modified as requested. Examine data fields 

in this status document for current requisition data. Also used by DAASC on DI 

AE9 to advise that the requisition contained an invalid/expired OSD/CJCS 

Category D project code. The project code has been blanked out and the 

requisition forwarded for processing." 

b. DLMS

(1) Implement corresponding procedures under DLMS establishing a 

unique status code exclusively for invalid/expired OSD/CJCS Category D project codes.

(2) Revise DoD 4000.25-M, Volume 1, DoD Logistics Qualifier Code 

Dictionary/Directory, Qualifier 81, Status Codes, as follows: 

CODE EXPLANATION

"** Requisition contained an invalid/expired OSD/CJCS Category D project code. 

The project code has been blanked out and the requisition forwarded for 

processing."

(** New code value to be assigned under DLMS)

c. Long-term. Implement OSD/CJCS Category D project code validation at the 

source of supply to include both new and back-ordered requisitions. Establish and maintain a 

single electronic source of project code information using a database to reflect current project 

codes, uses/refe rences, and duration dates, and other information as needed. Through this 

electronic database, the DoD ICPs and DAASC will have immediate automated access to current 

data. The specific method of providing interface (or data sharing) is to be addressed at a later 

date.

4. Reason for Change: The Air Force conducted a test on Project Codes in May 98 by 

directing DAASC to edit all Air Force “A0_”, “AM_”, and “AT_” transactions based on the 

latest J4 message of valid CJCS project codes. This edit rejected requisitions with 

invalid/expired CJCS project codes and provided data that showed AF compliance/noncompliance with current policy. DoD 4140.1-R directs that customers determine and 

communicate relative precedence of materiel requirements by application of priority designators, 

required delivery dates, and approved OSD/CJCS project codes. In addition, DoD 4000.25-1-M 

(Appendix B13) specifies criteria, responsibilities, controls, and methodology for determining 

assignment and use of OSD/CJCS project codes. The monthly reports to Air Force from their 

test resulted in changes to training programs and significantly reduced the number of 

invalid/expired CJCS project codes on AF requisitions. Since there were significant numbers of 

requisitions affected for the AF, it is most probable that there are also a number of requisitions 

with invalid/expired CJCS project codes from other DoD requisitions that are still being 

processed through the existing, non-edited requisition process. The AF briefed their findings to 
3

the DLMS Supply Process Review Committee during the 98-3 meeting. It was the consensus of 

the Committee that a proposal should be prepared by the Air Force for formal staffing. 

5. Advantages and Disadvantages:

a. Advantages: Current policy is that OSD/CJCS Category D project codes will be 

ranked above all requisitions with the same issue priority designator when system-wide supply 

inventory levels do not permit positive supply action on all requisitions. The proposed edit 

would ensure that the improper Category D project code assignments do not impact allocation of 

scarce resources. 

b. Disadvantages: None identified.

6. Impact: 

a. Publications: DoD 4000.25-1-M, MILSTRIP and DoD 4000.25-M, DLMS. 

Implementing Service/Agency publications as applicable.

b. Short-term Impact: DAASC program changes for requisition processing and edit 

table maintenance. 

c. Mid-term Impact: Modification ofService/Agency requisition processing to accept 

new DLMS status code. May require minor modification of the DAASC DLMS conversion 

process to convert the AE9/BK status to the new DLMS status code for DLMS users.

d. Long-term Impact: Development of single source project code database and 

automated interface for update of the DAASC and DoD ICP edit table s.