DEFENSE LOGISTICS AGENCY

 HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

 FORT BELVOIR, VIRGINIA 22060-6221

March 1, 2021

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC)

SUBJECT: Approved Standards Change (ADC) 1379, Establishment of a Warehouse Project 

Code (Supply)

The attached change to DoD Enterprise Business Standards, as outlined in the 

attachment, is approved for implementation. 

Addressees may direct questions to Rafael Gonzalez, e-mail: EBSO.Supply@dla.mil. 

Others must contact their designated PRC representative available at 

http://www.dla.mil/HQ/InformationOperations/DLMS/allpoc/. 

THOMAS A. DELANEY 

Director, Enterprise Business Standards Office

Attachment

As stated 

cc: 

ODASD(Logistics)

OUSD(C) 

OUSD(A&S/DPC)
Attachment, ADC 1379

Page 1

ADC 1379

Establishment of a Warehouse Project Code

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

a. Technical POC: Mr. Randall Reed, Leidos DPAS Program, 717-261-2602; or 

e-mail: randall.l.reed.ctr@dla.mil

b. Functional POC: Mr. Joseph Stossel, DLA J62 LCDS Portfolio; 571-363-8744; or 

e-mail: joseph.stossel@dla.mil

2. FUNCTIONAL AREA LOGISTICS AND TRANSACTION CHANGES: Supply

3. REFERENCES:

a. DLM, Volume 2 Supply Standards and Procedures, Appendix 2.3 – Ownership Codes

b. DLM, Volume 2 Supply Standards and Procedures, Appendix 2.4 – Purpose Codes

c. Approved DLMS Change 45, Use of Both Ownership and Purpose Code in DLMS for 

Ammunition, July 5, 2001

d. DLM, Volume 2 Supply Standards and Procedures, Appendix 7.13 – Project Codes

4. REQUESTED CHANGE(S):

a. Brief Overview of Change:

(1) This change establishes a new identifier called a warehouse project code. 

Warehouse project codes will allow materiel managers to distinguish materiel release and 

redistribution orders associated with specific programs, projects, or operations.

(2) This change also adds a DLMS note to authorize the use of a cost center 

in the Version 4030 DLMS 940R and 945A implementation conventions (ICs).

b. Background:

(1) The Defense Property Accountability System (DPAS) program office is 

requesting the establishment of a warehouse project code. DPAS will assign warehouse 

project codes to support the numerous DoD agencies and Military Services that use DPAS 

as an accountable property system of record (APSR).

(2) The DPAS suite contains a materiel management module for inventory 

control point (ICP) functions and a warehouse module for warehouse management. Using a 

materiel management role, authorized users procure materiel on behalf of one or more 

Military Services, and those Services fund their respective inventory. After procuring 

Service-funded materiel, DPAS reserves each Service’s respective balance in remote storage 
Attachment, ADC 1379

Page 2

activities. The remote storage activities segment the materiel by Service. In some cases, 

DPAS may need to further segment the materiel by program, project, or mission. 

Segmenting the materiel prevents one Military Service from requisitioning materiel reserved 

for another Service, or an activity within a Service from requisitioning materiel reserved for 

a different program, project, or property.

(3) To support this process, DPAS needs a method to identify which Service 

or Agency owns the reserved materiel. Ownership codes (Reference 3.a.) allow materiel 

managers to segment inventory balances for materiel owned by a Military Service or 

Agency. However, DPAS requires the capability to further segment inventory by program, 

project, or mission. Purpose codes (Reference 3.b.) provide materiel owners a way to 

identify the reason for reserving an inventory balance. However, purpose codes are 

assigned and used only on an intra-Component basis by the Component owning the 

materiel. DPAS does not own the materiel, and the current ownership code procedures state 

that further segmentation of these material by purpose code is neither prescribed nor 

intended.

(4) To overcome the limitations of the purpose and ownership codes, 

Approved DLMS Change (ADC) 45 (Reference 3.c.) authorized the Single Manager for 

Conventional Ammunition (SMCA) to use both codes at the same time within ammunitionrelated transactions. The SMCA manages materiel at the ownership code level. Similar to 

DPAS, the SMCA needed a way to identify and manage stock held for specific 

requirements. ADC 45 provided an example where the Navy needed to segregate assets 

funded and purchased with Special Warfare dollars. The SCMA-held assets were at its 

warehouses, and the Navy used requisition project codes to requisition assets against

specific requirements. In the example, the Navy managed to map the project codes to 

specific purpose codes. However, purpose codes are a one-position alphabetic value, which 

limits the available code values to 26. Furthermore, DPAS wants to avoid preventing the 

requisitioner from using a requisition project code for other purposes.

(5) Requisitioning activities use the requisition project code to distinguish 

requisitions to collect Service/Agency (S/A) performance and cost data related to distinct 

programs, projects, and operations. Defense Logistics Manual (DLM), Volume 2 Supply 

Procedures, Appendix 7.13 (Reference 3.d.) notes that S/As may assign Category A project 

codes when no meaning of the code will be perpetuated outside the originating S/A, or they 

may assign Category B project codes for use between one more participating S/As by 

agreement.

(6) Due to the limitations of the ownership and purpose codes, DPAS 

proposed creating a warehouse project code. The warehouse project code will function 

similarly to Category A and B requisition project codes. However, the warehouse project 

code will distinguish materiel release and redistribution order transactions rather than 

requisitions.

(7) Upon approval, this change will authorize S/As to assign warehouse 

project codes consistent with the procedures described in DLM, Volume 2, Enclosure 1. 
Attachment, ADC 1379

Page 3

Further use of the warehouse project code in additional transactions may be requested by 

submitting a proposed change. 

(8) In addition to the warehouse project code, DPAS requested a new 

identifier to indicate a cost center in materiel release orders. This cost center is not related 

to the identifier in the FA2 accounting segment of DLMS transactions. Instead, it represents 

cost center assigned to perform work within a remote storage activity. To satisfy this 

requirement, this change proposes adding a note to a DLMS data element called the

“Warehouse Pick Ticket Number” that explains its use by DPAS to identify a cost center.

c. Approved Change in Detail:

(1) Revise the DLMS 940R Materiel Release Order and 945A (Version 

4030) Materiel Release Confirmation ICs to include the warehouse project code, as shown 

in Enclosure 2.

(2) In the DLMS 940R Materiel Release Order and 945A (Version 4030)

Materiel Release Confirmation ICs, revise Qualifier WP – Warehouse Pick Ticket Number 

to include a DLMS Note to indicate that DPAS will use this the value to identify the cost 

center assigned to perform work at a remote storage activity. See Enclosure 2.

d. Revisions to Defense Logistics Manuals: Add new DLM, Appendix AP7.34 

Appendix 7.34: Warehouse Project Code as shown in Enclosure 1.

e. Approved Transaction Flow: This change does not introduce a new transaction 

flow, but it does add the warehouse project code to the DLMS 940R and DLMS 945A 

implementation conventions.

f. Alternatives: An alternative to this proposal is to expand the field size of the purpose 

code beyond one-position and allow alphanumeric entries. This alternative would also authorize 

the purpose code for inter-Component use.

5. REASON FOR CHANGE:

a. DPAS includes a materiel management module that allows users with the appropriate 

access to procure materiel on behalf of a Service or Agency, with each S/A funding its respective 

inventory allocation. For example, the materiel manager may purchase 50 widgets for the 

Marine Corps, 25 for the Air Force, and 30 for the Navy. To keep track of each Service’s

allocation, DPAS reserves a respective inventory balance in one or more remote storage 

activities. 

b. The warehouse project code will identify the specific program, project, or operation 

associated with the funding of the materiel. When DPAS receives a requisition, it will apply the 

warehouse project code associated with customer’s inventory allocation to the materiel release 

order. The remote storage activity will release materiel that is available within that customer’s 

allocation and provide a materiel release confirmation citing the customer’s warehouse project 

code. This will allow the materiel manager to update the customer’s balance against that 
Attachment, ADC 1379

Page 4

warehouse project code. If the customer’s requisition quantity exceeds the available balance, the 

materiel manager will notify the requisitioner of the unfulfilled quantity.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: DPAS will have an automated method to segregate Service-owned 

materiel against specific requirements.

b. Disadvantages: None identified.

7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: The procedures in this 

change are authorized upon release of the ADC.

8. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: None identified.

9. IMPACT:

a. New/Changed Data Elements: Add Warehouse Project Code as a new data 

element: to LOGDRMS per Enclosure 1

b. Automated Information Systems (AIS): DPAS will implement this change. Other 

AISs are authorized to implement this change upon release of the ADC, at the direction of their 

respective Component.

c. Defense Automatic Addressing System (DAAS): Update the DLMS 940R and 

945A maps for the materiel release order and redistribution order.

d. Non-DLM Series Publications: Non identified. However, DPAS will need to 

update their internal Standard Operating Procedures (SOP) to reflect the changes in this 

document. 

10. PROPOSED DLMS CHANGE (PDC) 1379 RESPONSE/COMMENT RESOLUTION:

Component Response/Comment Disposition

1. ODASD(Logistics) Concur without Comment As noted.

2. DLA Concur without Comment As noted.

3. Navy Concur without Comment As noted.

4. Air Force Concur without Comment As noted.

5. US Army Concur without Comment As noted.

6. USMC Concur without Comment As noted.

7. DAAS Concur without Comment As noted.
Attachment, ADC 1379

Page 5

8. USTRANSCOM Abstain As noted.

9. AFSAC None As noted.

10. DCMA None As noted.
Enclosure 1, ADC 1379

Page 1

Enclosure 1

Defense Logistics Manual (DLM) 4000.25, Volume 2, Supply Standards and Procedures 

Make the following changes to Volume 2. Add new Appendix 7.34.

AP7.34 APPENDIX 7.34

WAREHOUSE PROJECT CODE

NUMBER OF CHARACTERS: Three

TYPE OF CODE: Alpha/Numeric

EXPLANATION: Identifies materiel release and redistribution orders 

related to specific programs, projects, or 

operations. 

LEGACY RECORD POSITION: N/A

DLMS SEGMENT/QUALIFIER: N9 Segment, N901 Data Element ID 1270,

Qualifier P4 – Project Code

DLMS IMPLEMENTATION 

CONVENTIONS:

DLMS 940R Materiel Release Order, 

Redistribution Order

DLMS 945A Materiel Release Advice

AP7.34.1. Warehouse project codes distinguish materiel release and redistribution 

orders related to support of specific programs, projects, or operations. Applicable 

transactions include:

AP7.34.1.1. Lateral redistribution orders

AP7.34.1.2. Materiel release orders

AP7.34.1.3. Materiel release confirmations

AP7.34.1.4. Materiel release denials

AP7.34.1.5. Redistribution orders

AP7.34.2. A Service/Agency (S/A) may assign a warehouse project code when no 

meaning of the code will be perpetuated to another S/A. If multiple S/As are involved, 

the originating S/A may assign a warehouse code for inter-Component use if 

participating S/As agree to recognize the code value for a shared purpose.

AP7.34.3. Warehouse project codes are not related to requisition project codes (Refer 

to DLM 4000.25, Volume 2, AP7.13, Appendix 7.13.).
Enclosure 2, ADC 1379

Page 1

Enclosure 2

Revise X12 EDI Implementation Conventions as shown:

Changes are identified by bold italics and deletions by single strikethrough text.

DLMS 940R and 945A (4030) IC Revisions

# Location DLMS 940R Materiel Release Reason

1. DLMS 

Introductory 

Notes

Add ADC 1379 to the DLMS Introductory Note:

- ADC 1379, Establishment of a Warehouse Project Code

To identify changes made 

to the IC.

2. 2/N901/0400 Add Qualifier and DLMS Note:

P4 – Project Code

DLMS Note: 

1. Use to identify the warehouse project code. For 

requisition project codes use 2/LQ01/1300 qualifier code 

78. Refer to ADC 1379.

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

To allow a materiel 

manager to associate a 

materiel release order with 

a specific program, project, 

or operation. 

3. 2/N901/0400 Add DLMS Note:

WP – Warehouse Pick Ticket Number

DLMS Note:

1. Use to identify the picklist control number assigned to 

identify a specific job for which materiels are being

assembled together in support of planned maintenance.

2. Authorized DLMS enhancement under DLA industrial 

activity support agreement. Refer to ADC 381.

3. Used by the Defense Property Accountability System 

(DPAS) to identify the cost center assigned to a remote 

storage activity. Use 2/FA201/3000 qualifier code CC for 

the SFIS cost center. Refer to ADC 1379.

To allow DPAS to convey 

its cost center data element 

in materiel release orders.

4. 2/LQ01/1300 Add DLMS Note:

78 – Project Code

DLMS Note:

1. Use in redistribution orders, materiel release orders, 

disposal release orders and historical materiel release orders, 

but only to identify special programs, exercises, projects, 

operations, and other purposes. Use in materiel release order 

modifications to identify the revised project code.

2. Use of a project code in a disposal release order is an 

authorized DLMS enhancement; see introductory DLMS 

note 4b.

3. For DoD SLOA/Accounting Classification compliance the 

Project Code may be repeated as a Project Identifier (FA201 

Qualifier 90). Refer to ADC 1043.

4. For the warehouse project code, use 2/N901/0400 

qualifier P4.

To clarify that this is not 

the warehouse project code.
Enclosure 2, ADC 1379

Page 2

# Location DLMS 945A Materiel Release Advice (4030) Reason

1. DLMS 

Introductory 

Notes

Add ADC 1379 to the DLMS Introductory Note:

- ADC 1379, Establishment of a Warehouse Project Code

To identify changes made to 

the IC.

2. 2/N901/0400 Add Qualifier and DLMS Note:

P4 – Project Code 

DLMS Note: 

1. Use to identify the warehouse project code. For 

requisition project codes use qualifier 78 in 2/LQ01/1300.

Refer to ADC 1379.

2. DLMS Enhancement; see introductory DLMS note 5a.

To allow a materiel manager

to associate a materiel release 

order with a specific 

program, project, or 

operation.

3. 2/N901/0400 Add DLMS Note:

WP – Warehouse Pick Ticket Number

DLMS Note:

1. Use to identify the picklist control number assigned to 

identify a specific job for which materiels are being

assembled together in support of planned maintenance.

2. Cite the picklist control number in N903 due to field 

length.

3. Authorized DLMS enhancement under DLA industrial 

activity support agreement. Refer to ADC 381.

4. Used by the Defense Property Accountability System 

(DPAS) to identify the cost center assigned to a remote 

storage activity. Note: This is not the SFIS cost center.

Refer to ADC 1379.

To allow DPAS to convey its 

cost center data element in 

materiel release 

confirmations.

4. 2/LQ01/1000 Add DLMS Note:

78 – Project Code

DLMS Note:

1. Use to identify special programs, exercises, projects, and 

other purposes.

2. For the warehouse project code, use 2/N901/0400 

qualifier P4.

To clarify that this is not the 

warehouse project code.