Description
DoD Serial Number details not provided in "Custodian Inventory Report."  NAVFAC requires the USN in the serial number field, and VIN in the DOD Serial Number Field. Without VIN in DOD Serial Number Field, accurate verification of VIN against USN on vehicle assets cannot be completed. 

Recommended
Add DoD Serial Number Field to "Custodian Inventory Reports". This will allow accurate verification of VIN data against USN data on vehicle assets.

Mission Critical
No.  This is a matter of improving inventory accuracy. Having the DoD Serial Number Field made available on Custodian Inventory Reports would be extremely beneficial while conducting inventories on vehicle assets.

Benefits
Improves inventory accuracy and Reduces Time and Costs.

Users
Yes

Description
Currently while conducting an Individual or Unit issue there is no way to be able to edit an bulk item being issued and add a Serial Number to that item without having it serially managed in the catalog.  CSP is looking to remove the serialized managed from all E SAPI and Side SAPI plates  and make these items bulk managed, CSP would still need the ability to add a serial number during an Individual or Unit Issue process of a bulk item.  

Recommended
Recommend that during the Individual or Unit issue process the clerk will have the ability to be able to edit an item being issued out and add a serial number to that item being issued out, thus still giving us the ability to search by that edit box the serial number that the member was issued.  Also still need the serial number to be viewable on a members issue and outstanding items receipt. 

Mission Critical
Yes, having this process will help with the accountability and Physical Inventory process of serialized E SAPI and Side SAPI thus saving numerous man-power hours, but still keeping with the mandated policies and procedures sent by below email from Michelle at PM ICE:
concur with your plan to capture ESAPI serial numbers upon issue.  From PM ICE perspective, the purpose of serial numbers on ESAPIs is for tracking scanned plates' serviceability and identification of recalled plates.  As long as the NDTE machine is capturing serial numbers of scanned plates and every new plate is scanned -- along with capturing serial numbers of every issued plate, the requirement is met.   Also, NCIS appreciates when the CSP can track a stolen serialized plate to the last known user.  The USMC finds the most practicable approach to comply with PM ICE directives is to warehouse manage the assets as bulk and capture serial numbers upon issue/return.  

Benefits
Improve the accountability and Physical Inventory process of serialized ESAPI and SIDE SAPI's thus saving government Numerousness man-hours and costs. 

Users
All IIF/UIF

Marked Done - Change Request satisfied via other system updates per Rick McMillan 16 March 2023

Description
BSO's do not have the functionality to build appropriations (fund codes) within Master Data. In order for BSO's to fully control IUS Construction In Process, DPAS Roles will need to be modified.

Recommended
Recommend (WPUTN34 Appropriation) be added to the Navy PPM Role (DPAS 1024) and Accounting Role (DPAS 1190). The accounting role would allow BSO's to segment out CIP responsibilities within their organizations.

Mission Critical
No. However, with the upcoming requirement for BSO's to manage Capital IUS within the APSR, BSO's will require the ability to manage and monitor costs on all CIP Projects within their claimancy.

Benefits
This change request will save time and improve accountability at the Echelon II level for Capital IUS projects.

Users
This SCR will affect all BSO's who receive and manage CIP and IUS.

Completed – Release 6.0 – 27 April 2018

Description
There is a USMC requirement (Supply Order 4400-201, Chapter 9 and 13) to have a verification step during any quantity adjustments that occur in the DPAS application. Currently the only place that a quantity can be adjusted is in the inventory update manager.

Recommended
Recommend having a pop up that states "Are you sure you want to make this adjustment?" This is a generic enough statement to be used easily across the program, but will also meet the requirements that the Marine Corps requires. This will also reduce the amount of mistakes when adjusting inventory.

Mission Critical
This is mission critical due to the requirements of the Marine Corps to have this verification step.

Benefits
The benefits of implementing this solutions is that it would align all of the USMC Logistics Programs with Marines Corps requirements and the chance of improving inventory accuracy through verification during the quantity adjustment process. 

Users
This will affect all users who use the inventory update manager process to make inventory adjustments.

Removed per Norman Clark email on 5 June 2025

Description
Current policy requires that the Vendor's CAGE be entered as the Location of GFP/GFM that is has been sent to a contractor for use/repair.  This policy allows any person/auditor conducting an audit to know the vendor to contact to validate that they are in possession of the item being reviewed for existence & completeness.  Currently DPAS does not enforce this policy although the user is able to comply with this policy without a DPAS change.  AT&L PP&E policy office is requesting that DPAS modify it's system to better enforce the policy

Recommended
When performing an issue of GFM/GFP, move the CAGE from the Contractor record that is being associated to the Location field in the screen.  Upon the selection of update, if that CAGE is not currently a valid location, insert a new location record for that UIC using the supplied Vendor's CAGE noting that the location is a "Loaned" Type location (only used for when materiel/equipment is out on loan.  When the materiel/equipment is returned, check to see if this is the only item assigned this location.  If yes, remove the location from the location table.  If no, leave the location in tact.    
Note: This requirement needs to be addressed within the Materiel Mgmt / Warehousing modules when GFM/GFP tracking is implemented.  The outcome may be slightly different depending upon whether the organization is using the Materiel Mgmt module.  When the Materiel Mgmt module is used, then the Warehousing module would no longer have this materiel in inventory as it would have been issued.  Tracking may need to be accomplished by establishing a new RSA/C-ICP type.  When the Materiel Mgmt module is not used, then it may be possible to record this materiel as a "Unit Issue", but to a vendor (CAGE and/or DODAAC).The Warehousing / Materiel Mgmt changes may also require the adding of one or more GFM / GFP reports to provide the visibility of GFP/GFM.

Mission Critical
This change is being directed by the AT&L PP&E Policy Office.

Benefits
The change will improve overall accountability / visibility of GFM from within specific reports.

Users
Only those organizations with GFM/GFP will require this functionality.

Completed – Release 6.3 – 21 December 2018

Description
The Depreciation report can not be generate/run more than once a month.  Adjustments were made to the "Cost" field due to Examination results.  As a result the report is not correct for reporting purposes and month end  closing entries. In order to able to properly record the depreciation and reconcile the system it is necessary to be able to rerun the depreciation report.

Recommended
DPAS system have the capability to natively rerun the depreciation report.

Mission Critical
Not mission critical or mandated but will support FIAR efforts to validate DPAS capital equipment against accounting systems.

Benefits
Improves accuracy in reconciliations and Financial Reporting

Users
Only certain user are affected.

Description
DISA investment funding structure requires large volume and dollar value capital asset transfers between its general fund and its working capital fund.  Current DPAS functionality does not generate the needed accounting transactions to support this transfer environment.

Recommended
Request DPAS provide a radio button on the CIP Cost update to reflect whether to treat the adjusted cost amount as a “change” or a “transfer out” or “adjustment to a transfer out”.   A change would generate an X819A or M the way the process currently works.  A transfer out will generate an X817A for the difference between the old cost and the new cost.  An adjustment to a transfer out will generate an X817M  (Note: for a transfer out, the new CIP cost must be less than the current cost – an increase to CIP can never be a transfer out. An adjustment to a transfer out must always be an increase to the cost amount.)

Mission Critical
Mandated.  DISA is required under the CFO Act of 1990 to generate financial statements that can be audited. This change is required to accurately record the DISA investment funding structure for its capital asset purchases. 

Benefits
Improves efficiency, accuracy and financial reporting; current practice is a manual process. Process must be performed external to DPAS. Workaround within the DPAS system is not performed.

Users
Certain users affected.  DISA has a highly access controlled capital asset structure and procedures, due to the complexity of the capital asset composition and funding and the Departments demands on auditability of the Agency financial statements.

Description
Developing an option to "add an attachment" while conducting a transfer in the "Asset Management/Transfer" function.

Recommended
Add option to "add attachment" in "Asset Management/Transfer" function.

Mission Critical
No.  This is a matter of convenience and time saving.  Transfers are frequent.

Benefits
Reduces Time/Cost

Users
Yes it impacts all DPAS users.

21 Aug 2019 – cancelled per Kevin Callahan
No Longer Required.

Description
DPAS is not current compliant with DLMS ADC 295 that was issued on Aug 06, 2008.  DLMS ADC 295 requests all systems that support DLMS transactions to accept a Product/Service ID Qualifier of "ZZ" - Mutually Defined. 

Recommended
Modify the applicable DLMS transaction processes to accept a Product/Service ID Qualifier of "ZZ".  When a DLMS transaction contains a "ZZ" qualifier, take the Product/Service ID associated with it and check the DPAS Catalog for that value.  The internal business logic would be the same as for Product/Service ID Qualifiers of FS - National Stock Nbr and SW - Stock Number.  Retain the Product/Service ID Qualifier as part of the transaction that is captured in DAPS, and use the Product/Service ID Qualifier of "ZZ" to report back to the submitter where applicable rather than the Product/Service ID Qualifier applicable to the DPAS Catalog record.

Mission Critical
Failure to recognize the "ZZ" Product/Service ID Qualifier could result in DLMS transactions being rejected / failed when they shouldn't be / DLMS ADC 295

Benefits
Insures DPAS is DLMS compliant, ensure DPAS does not fail or reject a valid transaction.

Users
This change would impact any user who has an external DLMS feed from an external ICP or an external Remote Storage Activity (Warehouse).

Description
Due-Out Inquiry or Pending Transaction Report do not include the Ship To Address info (Activity Name, DODAAC, POC, Address, City, St, ZIP) as well as Phone Nbr, and Email Address.

Recommended
To include the fields mentioned above in the Due-Out Inquiry or have the Pending Transaction Report include this data which would be preferred in excel.  I would believe the Due-Out Inquiry would be the preferred method.

Mission Critical
With the majority of our transfers being outside DPAS it is critical to be able to track pending dispositions in order to follow up on delinquencies.

Benefits
Reduces time/cost and improves accountability.

Users
This would benefit all users within our component and agency.