Unlike submitted Support help tickets, System Change Requests (SCR's) can only be submitted through your organization's appointed and authorized ELMS CCB member representatives, or otherwise if no CCB representatives have yet been appointed, your Primary Information Owner appointee. If you are unsure of who your organization's appointed ELMS CCB member representatives or Primary IO are, you may email the ELMS Support team to request that information:
To learn more about the process, please visit our CCB Responsibilities and Meetings page. Below you will find all SCR's that have been submitted, and what their status is. To download a blank form, you may visit our Reference Library and download the SCR Form.
Utilize the search filters below to narrow your results by keywords, module, or state. You may also request an Excel file of all the SCR data by contacting the Help Desk.
| Found: 1807 Result(s) | Show: |
| Title |
ELMS Module |
Reporting Org |
State |
Description |
Action |
|
|---|---|---|---|---|---|---|
| 01904 | DPAS to DAI Interface Codes | PA | Done | Description:
When the interface was established with DAI, it was determined that DAI was unable to receive x806, x813, and x814 transactions, so DPAS sends x805 transactions instead. This deviation of the crosswalk is causing DFAS to record any and all dispositions with a JV because the transaction code DPAS is sending to DAI is different from the transaction code being recorded within DPAS.
Recommended:
DPAS needs to revise their crosswalk for the DAI interface, so x806, x813, and x814 transactions are sent to DAI so we are in conformance with U.S. Treasury’s guidance for the disposition of an asset with a loss.
Mission Critical:
This is a mission critical function as it is causing journal vouchers to correct.
Benefits:
The benefits of this change will bring the interface into conformance with U.S. Treasury’s guidance for accounting for property losses. It will also eliminate the need for journal vouchers to be processed in DAI for the improper transaction code being sent today.
Users:
Will affect all users within DFAS.Completed – Release 2024.2.3 – 03 May 2024 |
||
| 01903 | Warehouse Management Physical Inventory Role | Warehouse | NSWC-SPECWARCOM | In Progress | Change Request: New Role Design
Description:
Currently there are no roles that limit a Warehouse User to downloading released physical inventories, conducting the physical inventory, then uploading completed physical inventories using the automated capabilities of DPAS
Recommended:
Create a new Warehouse role that is limited to downloading, conducting and uploading completed inventories along with any system changes that are needed to limit the user to conducting physical inventories only
Mission Critical:
There are users whose sole DPAS responsibility is to conduct and report the results of a physical inventory.
Benefits:
Ensure Separation of Duties are enforced.
Frequency: Weekly
Users:
This role will enable separation of duties and limit users who conduct physical inventories to those functions within the DPAS warehouse management application.Partially Completed – Release 2023.2.5 – 02 June 2023 |
|
| 01902 | Maintenance Parts Mgmt interface with Discovery and Advana | MU | USAF: VSCOS | New | Change Request: Process Improvement
Description:
CURRENT deferred workload is incorrect. DPAS drops the connection between the Warehouse Parts order data and the M&U Work Order data once the part is received in
Warehouse and they create a DUE-IN for it. DPAS doesn't go back and update the Deferred Work Orders to mark them as being completed. They are marked CLOSED, but not COMPLETED. We need to get all the warehouse parts data and implement the correct logic on the Advana/BLADE QLIK side of the house.
Recommended:
AF require DPAS to provide BLADE with ILS-S requisitions, DPAS Warehouse Maintenance Issue orders, and the parts that have been associated to a Work Order, and ensure the capability to defer a part does not cancel the part (It removes the WO Number from the order if there is one assigned, but keeps the part associated with the Task and Asset.). Also insure that when a deferred task is added to a new WO, that the deferred task is closed.
Mission Critical:
The 441st VSCOS in the AF deem it as mission critical, as they need this data to sufficiently manage the vehicle maintenance workload.
Benefits:
Improves accountability.
Frequency: Daily
Users:
All users
This change effects the interfaces with Discovery and Advana, along with reviewing / modifying the management of parts within Maintence, Requisition and Maintenance Issue. |
|
| 01901 | Qty Receipt for Serial Managed Local Due Ins | PA | AF: A4/HAF FH-AFHAF | New | Change Request: Process Improvement
Description:
When a requisition for a quantity greater than 1EA in ICP the system then sends multiple'local Due-in' to PA for receipt processing using the same document number that was initiated. Foe example processing a requisition for 10 EA, 9mm weapons, in PA 10 individual local Due-in are established. Additionally the system will not allow for the quantity to be updated when processing the receipt, requiring each due-in to be processed individually.
Recommended:
Establish the local Due-in in PA for the same quantity that was initiated in ICP. Allow for multiple serialized assets to be received under the same document number.
Mission Critical:
Benefits:
Reduces processing time by eliminating multiple individual transactions.
Frequency: Daily
Users:
All users that are utilizing ICP to requisition for PA |
|
| 01900 | WM to MU Maintenance Request | Enterprise | Leidos | In Progress | Change Request: Process Improvement
Description:
The modernization of the Maintenance and Utilization (M&U) module requires the 2-way communication between the Warehouse Mgmt. Quality Control processes and M&U work order processes to be reworked.
Recommended:
Update Warehouse Mgmt. to utilize the Maintenance and Utilization mico services that have been fielded for M&U.
1. WM sends a request to M&U requesting a service to be performed.
2. M&U creates a Work Order to have the type of action requested performed.
3. When the work requested has been completed, M&U informs WM that the work has been completed.
4 WM creates a QC action to have the work performed reviewed for completeness.
5 .If work is incomplete, a request is sent to M&U to have the WO reopened.
6 Process continues to recycle until WM QC signs off that the work requested has been completed.Mission Critical:
This is the technical solution only, to modernize the technical communication between the modules. Any functional redesign of the user process will be handled through the modernization of WM as priority dictates.
Benefits:
Provides users of the Warehouse Mgmt. module to request services of the M&U module user in support of: prep for ship, prep for stow, and COSIS.
Frequency: Daily
Users:
This will affect all users utilizing both WM and MU, and work orders, to perform maintenance on their assets. |
|
| 01899 | Medical Logistics Systems Catalog Interface | Enterprise | New | Change Request: Process Improvement
Description:
There is currently no tie to the DLA medical logistics systems as there is with WEBFLIS/FEDLOG. Propose that there be an option to feed the DPAS catalog with data from the below sites to ensure current NSN data is populated in the catalog:
https://www.dla.mil/Working-With-DLA/Applications/Details/Article/2922517/dmmonline-dla-medical-master-online/
https://www.medical.dla.mil/SSO/consentRecommended:
Create a linkage between the medical supply information systems to the DPAS catalog.
Mission Critical:
Prevents users from looking in multiple DLA systems for information to manually update the catalog.
Benefits:
Time savings with automated updates to the catalog. Centralizing would benefit all 4 branches of the DoD.
Frequency: Daily
Users:
The effect would impact anyone managing medical supplies in DPAS Warehouse Module. |
||
| 01898 | Client RSA load from PA Master Data | Enterprise | AF: A4/HAF FH-AFHAF | New | Change Request: Process Improvement
Description:
Currently when loading a new UIC in PA, the user is also required to ensure the client RSA is established in ICP in order to requisition property. Additionally, the current process to manually load a new Client RSA is to submit a trouble ticket to the Help Desk which has taken several week to accomplish
Recommended:
Establish an automated process where the Client RSA is also established when a UIC is loaded into the Master Data file in PA.
Mission Critical:
By design DPAS requires an ICP Client RSA to be established in order to requisition property.
Benefits:
This eliminates the requirement to submit a trouble ticket every time a new client RSA needs to manually loaded in ICP when a new UIC is established.
Frequency: Monthly
Users:
All users of ICP module for requisitioner capability for property that reside in PA. |
|
| 01897 | Money Value Gain Loss Notice | Materiel Management | USMC: CSP | Done | Change Request: Policy/ Regulatory
Description:
Request for DPAS-WM to provide the ability to search items have been gained and lost from the warehouse, for a specified date range and enterprise level, and be used to generate a Money Value Gain Loss Notice (MVGL/N). The date range capability is to permit the user to able to create an inventory adjustment report that spans multiple business days. Having the capability to include multiple days of activity in a single report will streamline the review and certification requirement.
Recommended:
Create or modify an existing inquiry to allow the ability to select the date range, required adjustment codes and columns necessary for the notice. The inquiry allows an enterprise view, based on user security access. The inquiry will provide the ability to export the results to an MVGL/notice which is required to include the following statement: "I have reviewed the documents on this notice and verify that required documents have been properly certified." - to be certified by the CO/Accountable Officer or acting CO/Accountable Officer. The notice will be emailed out for digital signature and a repository, within DPAS, will be provided for upload and archive for up to 2 years. The notice must contain at minimum, the following fields: DODAAC, DIC or DLMS Identifier, NSN, UI, Document Number, and Condition Code. The data needs to be able to be exported with a signature block for command signature.
Mission Critical:
This change is requested to facilitate USMC in adhering 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. The current DPAS MVGL process does not provide the functionality requested by USMC.
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.
Frequency: Daily
Users:
This will impact all users who process inventory transactions within the system.Partially Completed – Release 2024.3.1 – 12 July 2024
Partially Completed – Release 2024.3.2 – 26 July 2024
Completed – Release 2024.3.3 – 09 August 2024 |
|
| 01896 | Supply Category Management Code | PA | Army: ASA(ALT) | Done | Change Request: Process Improvement
Description:
ASA(ALT) utilizes the DPAS PA module to perform Total Package Fieldings (TPFs). The Supply Category Material Code (Sply Cat Mat Cd) is required, this field initially appears when receiving an asset into the PA module when entering data such as the NSN; however, is not visible in the asset’s record afterwards.
Recommended:
Army is requesting that DPAS make this field visible in the asset’s record in the PA module, on the BASIC screen, for our management purposes including but not limited to queries, reports, etc.
Mission Critical:
Visibility of this code in the asset’s record ensures compliance with DoD and Army policy in that only equipment meeting the criteria as accountable property is recorded in the APSR (PA module). The presence of this code in the asset’s record enables the ability to establish and execute internal controls validating this policy requirement and audit readiness
Benefits:
This process will allow us to better manage our equipment within DPAS and support our TPF mission, as well as meet OSD/Army Policy.
Frequency: Daily
Users:
This feature will be utilized by the ASA(ALT) PMs in fielding of the next generation of equipment to the U.S. Army and by USSOCOM for TPF processes.Completed – Release 2023.4.2 – 20 October 2023 |
|
| 01895 | DPAS Access Roles Request Automation | Enterprise | Navy: NECC | New | Change Request: Process Improvement
Description:
The Role Request as part of the DPAS WM access request process has inefficiencies in that the the packages get rejected for an incorrect LP, Region, Site, or Warehouse names. Rightly so, but this greatly delays the process by recycling the requests to start from the beginning. The IO /AIO has final approval to grant roles, so ultimately it should be up to them and should be accessible within the system as long as the DPAS Role training is complete, cyber-awareness training requirement met and SAAR approval process completed. The DPAS Role Request form itself may be worth improving to cut down waiting time due to emails that address errors and rework for errors that could be avoided from simple process improvement.
Recommended:
1) Automate the assignment of Roles in DPAS via an internal LP request to an IO/AIO or process that generates an email to the person(s) controlling the LP / Region / Site / or Warehouse requested to notify them to review their request.
2) Alternate option: Create a PDF Role Request form that can has LP structure of all organizations to provide drop down options on the form. This would remove errors that come from the end user or oversights from IOs/AIOs. Too often an error, even an insignificant grammatical error will cause a DPAS system access delay in excess of one month.
*Side note-automated Online SAAR form using digital signatures may also be worth pursuing.Mission Critical:
The time savings of emails, status requests, and rework for all involved in the DPAS access request would take out the frustration of the process because it would remove the ability to make errors.
Benefits:
This is the first impression of the DPAS user to the DPAS System and if this becomes is relatively quick and painless, the user may perceive the system itself in the same way. I cannot tell you how many people get frustrated with the initial inefficiency and immediately assume the product to be bad too, which in my opinion is NOT the case.
Frequency: Daily
Users:
This would be of benefit to all DPAS WM IOs, AIOs, and the DPAS Security Team. |
Disclaimer | Accessibility
Please be advised that Navy Property Accountability module users will be unable to access ELMS during the period beginning 3pm EST on Tuesday September 29th, until 8am EST on Friday October 2nd due to the annual EOFY lockout period. If you have questions, please direct them to the Navy PP&E Management Support Office via their centralized email inbox, which is
Please be advised that ELMS will be unavailable beginning Friday, October 2nd at 9:00 pm EST for server maintenance. Estimated downtime is stated to last up to 60 minutes in length - please plan accordingly.