Currently DPAS Account Management sees the Warehouse user accounts by going to the User Management screen. To get to this screen we go to Security Mgmt and select User. Currently there is no way to see the users by Logistics Program. I've had to generate the results on this screen and export the information and go through and manually look through the email addresses to provide user reports. This is time consuming and cumbersome.

Recommended solution
On the User Management screen, add a Search Criteria filter for Logistics Program. We get to this screen by going to Security Mgmt and selecting User.
SCR00605 is for an inquiry that shows every Logistics Program, Region, Site and Warehouse assigned to a user. In theory SCR00605 will show a user multiple times depending on the access granted. This request will only show each user one time. If they have access to two Logistics Programs then the other Logistics Program would need to be selected and they would show up under the other Logistics Program as well.
I would also like to request columns be added for Last Logistics Program, Last Region, Last Site and Last Warehouse. This information is available on the User Account Inquiry in the PA module and has proved to be beneficial. Not only on a daily basis but this is needed for conducting the annual audits. This inquiry should be available for Security and any Standard User assigned the Admin Reports Role. The user should only be able to see the results for their Logistics Program, Region, Site and Warehouse assigned, depending on the Level of Access granted.

Customer priority: 2

Monday, November 14, 2016:
Marked as included in 4.0

Description
The requirement exists for the system to breakout outstanding returnable items by individual issue, temp loan, and unit issue.
These are separate requirements, and should not appear on the same form.
More details are provided below:

• Individual Issue
  Gear issued from an individual issue facility
• Unit Issue
  Should be a UIC report, separated by the RO that drew the gear.
  Same report, but with a means to separate the RO who signed for the gear and a roll up.
• Temp Loan
  Should be a separate form as well

Recommended
It is recommended that separate reports be generated, per user/instance, in order to process returns. If an individual has equipment on temporary loan, unit issue, and individually issued to him, than those outstanding returnable items should be listed on three different reports.

Mission Critical
This is mandated due to current CSP standard operating procedure.

Benefits
Equipment accounting and the returns process will both be enhanced after this change is implemented.

Users
This will affect all CSP customers and will also affect all warehouse managers.

Completed with SCR 00757.

The EAS Alert should only notify the system user of members who have equipment and their EAS is near expiring, vice simply showing that a members EAS is expiring. EAS expiration is only a problem if that member has equipment.?

 Completed – Release 2022.1– 08 April 2022

Description
The requirement exists for the system to allow users to view the current outstanding returnable items list, and all historical issue and return receipts with emphasis on the current receipts.
This is a big deal for the system to have due to the fact that users will often challenge what they have issued to them. It is imperative that the system users be able to show Marines where they signed for items, and what they signed for. Must be able to see when the Marine Came in, and all the details around the visit.

Recommended
It is recommended that a way to view historical issue and return results, per user, be developed in order to allow users to show customers their customer history.

Mission Critical
This is a critical change in order to further improve this overall. This change will benefit issue process.

Benefits
This change will benefit all users and aid in any form of causative research.

Users
All users involved in issue/return processes will be affected by this.

Completed - Release 3.2 - 06 January 2016

Description
The requirement exists for us to be able to mass print location labels, ICN Labels, Container Labels, and Stock Number Labels for a warehouse. The system should be designed to support the printing of all WH Labels or select WH Labels en masse.

Recommended
Develop a process in order to mass print all location labels, container labels, and stock number labels.

Mission Critical
This change is critical.

Benefits
This change will dramatically reduce the time necessary to print all labels for a warehouse.

Users
All warehouse users will be affected.

The requirement exists for system managers to be able to measure the metrics of how long an issue, return, exchange, or temp loan is taking them in the system. ?To fulfill this requirement, it is requested that each of these processes be modified to include the start time (time when the issue, return, exchange, temp loan) is started to the time the process is completed in the system (When the member signs and the receipt prints.) This metric should be recorded on all issue/return/exchange/temp loan receipts and should be available as a grid option within the menu of each of these processes. ?In addition, the metric should be available on the issue/return activity report to aid in the determination of customer processing time across the CSP enterprise.

11 Mar 2021 – cancelled per Jack Sanders
No Longer Needed.

Description
It is a critical system requirement that the DPAS-WM produce a daily Money Value Gain Loss Statement showing which items have been gained and lost from the warehouse on a daily basis. Additional info on the report is provided as follows:
Purpose: Money Value Gain Loss Notice (MVGL/N). This report contains a listing of all gains/losses processed. The notice will have the following statement certified by the CO/Accountable Officer or acting CO/Accountable Officer: "I have reviewed the documents on this notice and verify that required documents have been properly certified."
The MVGL must have the following minimum data elements:

• DODAAC
• DIC or DLMS Identifier
• NSN
• UI
• Document Number
• Condition Code
• ICN
• QTY
• Extended Price

Summary Info: Total Gains (Any gain made for admin or discovered item purposes) Total Losses (All losses made via inventory manager update, or losses recorded on returns in the system). Additionally, the MVGL must have the following statement and a signature block: "I have reviewed the documents on this notice and verify that required documents have been properly certified."
Frequency: This report is a summary of all DAILY gains/losses processed by a warehouse. It must be signed by the Commander Officer or Designee to validate that all gains and losses are backed by proper documentation.
Duration: Per the MCO 4400.150F this report must be kept on hand for 2 years.
Additional Info: It is requested that the signature of this report be capable of e-sign or electronic signature pad as we have, or are requesting, in other processes. The Commanding Officer or Designee will need to have a role in the system for them to sign and reconcile.

Recommended
There is currently no way within the system to adhere to MCO 4400.150 in regards to MVGLs. All appropriate inventory gains and losses must be signed by an accountable officer before they are processed. Currently this mandatory function does not exist within the system.

Mission Critical
This is a mission critical item. This function is a basic Supply Procedure and is necessary to ensure accountability across the enterprise.

Benefits
This change will provide a simpler way of accounting for loss and gain transactions. As it stands now this process is accomplished by means outside of the system. Incorporating this within the warehouse module will save time and help eliminate human error.

Users
This will impact all users who process inventory transactions within the system.

Partially Completed – Release 2022.1.1 – 22 April 2022

Completed – Release 2022.1.3 – 03 June 2022

Description
We need to generate history transaction reports for Account Management, users and system generated in-activations and deletes. These items must be reviewed by the Information System Security Manager. This will ensure we are in compliance with the DIACAP control ECTP-1 and NIST Publication 800-53 AC-6-Least privilege.

Recommended
Develop history reports to capture any account related transactions. On the PA side the following history reports are being used:

1. Deleted User History – This shows every user that has been deleted by Account Manager or the system when the account reached 45 days of inactivity. – The fields on this report are:
• DPAS User Id,
• User First Name,
• User Last Name,
• Agency Cd,
• Agency Name,
• Site-Id,
• Last Updated By,
• Last Tran Dt,
• History Remarks
2. User Actbl UIC History could be replaced with User Region History. – This shows every user’s Actbl UIC access that was added, updated or deleted by Account Management or by the system when the account was deleted at 45 days of inactivity. – The fields on this report are:
• User Id,
• First Name,
• Last Name,
• Site-Id,
• Actbl UC,
• Tran Cd,
• Last Updated By,
• Start Date,
• History Remarks
3. Users History – The results for this inquiry are very large. We need filters to remove some of the unwanted results. – The fields on this report are:
• User Id,
• First Name,
• Last Name,
• Site-Id,
• Tran Cd,
• Status Cd,
• Status,
• Last Updtd By,
• Last Tran Dt
• History Remarks
The report shows:
• Every normal login made by the user.
• Every account created or updated by Account Management.
• All normal user logins.
• Every time a user changes Site-Id and Actbl UICs.
• The system generated email sent at 15 days of inactivity.
• The system generated emails sent to every user at 30 days of inactivity.
• The system generated email sent at 45 days when the account is deleted.
4. User Property Custodian History – This shows every Account Management add, update and delete. When a user’s UIC is deleted by Account Management it shows every system delete transaction for each custodians being deleted from that user’s account. It also shows if a custodian is added, deleted or modified by any user on the application. This also is a very large inquiry and filters are needed to reduce the data results. – The fields on this inquiry are:
• User Id,
• First Name,
• Last Name,
• Site-id,
• UIC,
• Custodian Nbr,
• Sub Custodian Nbr,
• Tran Cd,
• Last Updated By,
• Start Date,
• History Remarks.
5. User Role History – This shows every role added, updated or deleted from the users account. This shows the system deleted the account at 45 days of inactivity. A 2nd email is sent cancelling the user. I’m not sure what the difference is between system deletes and system canceled but it includes both. – The fields on this inquiry are:
• User Id,
• First Name,
• Last Name,
• Site-Id,
• Role Name,
• Tran Cd, Status,
• Last Updated By,
• Start Date,
• History Remarks.
6. User Site History – This shows every normal login. This shows every time a user switches a Site-Id or Actbl UIC. This shows every site added, updated or deleted by DPAS Account Management. It shows when an account is cancelled and the email sent. – The fields on this inquiry are:
• User Id,
• First Name,
• Last Name,
• Site-Id,
• Tran Cd,
• Site Last Login Dt,
• Last Updated By,
• Start Date
• History Remarks.
7. Users UIC History – This shows every UIC added, updated or deleted by DPAS Account Management. It also shows the systems deletes and the system cancellations. It also shows every UIC added or deleted by a user. – The fields on the inquiry are:
• User Id,
• First Name,
• Last Name,
• Site-Id,
• Actbl UIC,
• UIC,
• Tran Cd,
• Last Updtd By,
• Start Date
• History Remarks.

Mission Critical
Yes, it is required to pass the upcoming SSAE 16 audit in June.

Benefits
We will be able to provide the appropriate information for the audit.

Users
This SCR is to be incompliance of required controls so we can pass the SSAE 16 audit.

Completed - Release 3.0.01 - 02 June 2015

Description
Last week MPB (SCS) was able to complete changes in production which will allow direct D8 and D9 adjustment transactions to process and suspend within the accountable system of record. As such, we will be doing away with the requirement to send count cards back to SCS (MPB) as a result of a DJA request for inventory.

Recommended
The following change to the inventory process must occur in DPAS. Once an adjustment to the record has been approved by the custodial approving official (DMC), DPAS should immediately adjust the custodial record. At the time of the adjustment (D8/D9) in DPAS, the associated 947I (D8/D9) should be transmitted to MPB.

Mission Critical
 

Benefits
Complies with DLM4000.25 series

Users
Yes

25 June 2020 – cancelled per Ryan Steele
No Longer Required.

Need project code on the Grid line so it can be used as a searchable field and be seen without opening the expansion arrow. The project code needs to be available on the grid line when approval processes are performed.