Description
we are not able to set appointment time because appointment intervals are mandatory.

Recommended
provide ability to have set appointment times versus appointment intervals

Mission Critical
important

Benefits
Ability to schedule more than one different class when they have a different start time. 

Users
all AFERMS

Completed – Release 2022.2.2 – 23 September 2022

Description
Size category generates a walk in even if you are doing an admin only.

Recommended
add check box or drop down for admin only when scheduling is in use.

Mission Critical
important

Benefits
Ability to schedule more than one different class when they have a different start time. 

Users
all AFERMS

Completed – Release 2022.1 – 08 April 2022

Description
Currently, the Consolidated Storage Program (CSP) has a problem with Marines leaving active duty service with gear on their account. The CSP has been writing this gear off during the their annual audits, but there is a desire to create an End of Active Service (EAS) inquiry that will show all the returnable assets on a Marines account when they hit a predetermined amount of service time left.

Recommended
Create an EAS Inquiry that will populate all the items left on a Marines account when they are 180 days away from their EAS date. Having a six month time frame will ensure that the Marines are notified well in advance of their exit date. 

Mission Critical
Yes, this inquiry will allow the CSP to notify the Marines of outstanding issues, which in turn will hold the Marines accountable to turn it in before leaving the service. This will also allow the CSP to conduct analysis on the each warehouse and the amount of outstanding gear not turned in.

Benefits
Implementing this inquiry will help reduce the amount of gear that is lost due to Marines who leave the service with outstanding turn ins. That directly affects financial cost due to having to replace lost/missing gear.  

Users
This will effect all CSP Users and the customers we issue gear to.

Completed – Release 2022.1 – 08 April 2022

Description
Currently, when the Consolidated Storage Program (CSP) moves items that have a manufacturer lot and contract number they have to write those attributes on the pick ticket. Would recommend these fields be included on the pick sheet so they will no longer have to manually write it.

Recommended
Include the manufacturer lot and contract numbers on the pick ticket that is generated. If the asset is not lot or contract managed then the fields can be blank.

Mission Critical
Yes, including these attributes will save CSP users time when moving assets within the warehouse.

Benefits
Including these attributes will save CSP users time when moving assets within the warehouse.

Users
This will effect all CSP Warehouses.

Partially Completed - Release 2025.1.5

Description
Authorizations are redundant and problematic in PA for centrally managing authorization quantities and overall force management. 

Recommended
Move all PA authorizations to FSM.  Stock Number Authorizations and LIN/TAMCN Authorization for more cohesive management.  

Mission Critical
Yes for tech refresh.  

Benefits
Mass update capabilities, unit deployments, Theater Force Management.  

Users
No

Partially Completed – Release 2022.2 – 26 August 2022

Partially Completed – Release 2022.3.1 – 18 November 2022

Partially Completed – Release 2022.3.2 – 02 December 2022

Description
This SCR implements the Project Code change identified within ADC 1379.  For the Cost Center change identified within ADC 1379, reference ASA(ALT)'s DPAS SCR 01562.  Project Code requirement - USSOCOM purchases service funded inventory.  Once it arrives and is placed in stock, each service's inventory is given a different project code to identify the qty that each service has purchased and will be subsequently issued. Today, there is no capability to pass a requisition Project Code (why the customer is ordering the item) and the Project Code that is assigned to the inventory (what stock needs to be selected to fill the order).  Today to support sending the warehouse project code, the customer cannot cite a project code in the order.  To support USSOCOM's requirement of segregating the inventory, there was a need for the second Project Code to be included in the messaging between the Materiel Mgmt and Warehouse Mgmt modules.

Recommended
Warehouse Project Code - Within Materiel Mgmt., include the warehouse and requisition project codes in the DLMS 940R transaction that is sent to the warehouse for fulfillment.   For the Warehouse, process the inbound 940R adding the warehouse project code to the MRO.  Then use the warehouse project code to determine stock availability and to feed to Materiel Selector and in the creation of the Pick row that is subsequently created.  On the outbound DLMS 945A distinguish include the requisition's project code and the warehouse project code. Use the warehouse project code to decrement stock in Materiel Mgmt. upon receipt of the DLMS 945A confirming the shipment of the stock. The DLMS 856S shipment status will contain the requisition project code.   When the order fulfillment is to occur with inventory consisting of multiple warehouse project codes, permit the suffixing of the Document Nbr to enable multiple MROs to be generated to the same RSA, each with a different warehouse project code. This change may require a change to the Picking process.

Mission Critical
Yes.  USSOCOM requires a method to mange their inventory by the organization that purchased it.

Benefits
ADC 1379 eliminates the confusion between the requisition project Code (why the organization is ordering the item) and how the warehouse is storing the item.  The Materiel Manager / Warehouse operations will now be able to segregate the materiel without having to email/notify the warehouse which stock to select to fill an order.

Users
Most warehouse operations will benefit by this change.

Description
Currently, during the individual return process all MILSTRIP transactions created for lost gear is a D7A. This MILSTRIP Transaction does not meet Marine Corps Standards for audit. The concern is that a D7A is an issue transaction instead of a loss transaction, which is what the Marine Corps needs to see during audit inspections. The attached spreadsheet is the preferred MILSTRIP transactions the Marine Corps would prefer to see be created when an individual doesn't return gear. This would make the non-returned items audit compliant.

Recommended
Change the non-returned items reason codes MILSTRIP transactions to match the values in the attached spreadsheet. 

Mission Critical
Yes, this would ensure that a MVGL would be generated for the correct non returned reason codes when that SCR is put into production.  These transactions on the MVGL would ensure the commander would correctly identify losses when vouchering the MVGL.  This would make them more accurate and meet audit standards.

Benefits
This SCR improves accuracy, accountability and audit readiness/financial reporting.   USMC audit keys in on correctly identifying losses, and the causes of those losses.   Being able to quickly identify losses due to non-return of previously issued assets, would be a significant improvement to the audit process. 

Users
This will affect all users in CSP and should be a net benefit to other services and organizations that issue equipment as well. 

Removed per Norman Clark email on 5 June 2025

Description
Currently, the Consolidated Storage Program (CSP) doesn't have an interface for financial transactions. In October 2021 the Marine Corps will move from the Standard Accounting, Budgeting, and Reporting System (SABRS) accounting system to Defense Agencies Initiative (DAI) Enterprise Resource Planning (ERP) system.  We would like to interface the new Marine Corps accounting system (DAI) with DPAS. This will allow for transactions to flow seamlessly between systems, unlike the current process that demands ordering through DPAS and then "Swivel Chairing" to SABR's to obligate funds.

Recommended
Create an interface between DPAS and DAI. Currently GCSSMC is looking at creating a outbound XML file using the "piping" delimiter as field separator. DPAS should be able to follow a similar business process. 

Mission Critical
Yes, interface would help ensure accuracy for obligating funds and save personnel work hours.

Benefits
This interface would help ensure accuracy for obligating funds and save personnel work hours.  This would also be a significant improvement for audit. 

Users
This will effect all CSP Warehouses that order assets.  This will likely be a net benefit to other services and organizations as DIA is not USMC specific. 

Description
Need to add location and container to the Repair Part Consumption Report.

Recommended
Under Repair Part Consumption Report, we need to add two columns, one for Location the repair part was pulled and the same for the Container the repair part was pulled.

Mission Critical
YES! Warehouse technicians have no idea where the part was pulled from to receive it back to once the part is placed in due out status. Also if a container is deployed and it returns, you understand on what is needed to refill the deployed container.

Benefits
data accuracy.

Users
All

Completed -- Release 2021.2 - 28 May 2021

Description
Due to an audit finding we have an issue where the document number and obligating document number in DPAS only transfers to eBiz with the x819 transactions.
The document number and obligating document number for x815 and x817 transactions do not appear on the interface file as these fields are currently optional.

Recommended
The document number and obligation document number for x815 and x817 transactions should be mandatory and pulled in on the interface file to e-Biz to populate the Register Document Number in e-Biz.

Mission Critical
This is a mission critical function as it is causing an audit finding.

Benefits
The benefit of implementing this change will reduce process time for accounting technicians to manually input the document number for capital transactions.  Additionally, it will improve the accuracy of the financial statements because eBiz will receive the data from DPAS and reduce the risk of input errors.

Users
Will affect all users within DFAS.

Completed – Release 2021.4 – 17 December 2021