System Change Requests

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: This email address is being protected from spambots. You need JavaScript enabled to view it..

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: 1779 Result(s)	Show:

Scr Number	Title	ELMS Module 7,5,4,2,8,1,6,3 1,1,1,1,1,1,1,1	Reporting Org	State	Description
02126	Mass Appropriation Update Interface Code Improvements	PA	Leidos	New	Change Request: Process Improvement Description: Mass Appropriation Update only supports moving to fund codes that follow the same interface system code. Most Accounting systems require cost elements that do not lend them to an automated transition from one accounting system to another. The AY (no automated interface) and AG (GAFS-R) accounting interface does not require cost elements, thus the Mass Appropriation Update process should permit the user to update the interface system code when the from or to is either AY or AG. Recommended: Update the Mass Appropriation Update program to allow users to update DPAS supported accounting interfaces to accounting interface cd of "AY" (No Automated Interface) or AG (GAFS-R) . Mission Critical: Mass Appropriation Update currently exists but is limited by its current design. This change will enable users to perform the update without customer support / scripting by the DPAS support teams. Benefits: Users can handle mass appropriation updates that involve AY or AG without having to request scripts that have the possibility of handling thousands of transactions. The functionality is already largely in the program, it just needs improved to support different accounting interfaces. Frequency: Daily Users: Many users use this program and can use it at any time. The job runs daily through queued appropriation updates.
02125	LDAC Data Modification	PA,Warehouse,Materiel Management	US Army	New	Change Request: Process Improvement Description: LDAC is requesting a modification of the data elements we are currently getting daily from DPAS. These additional data elements are required to start the development / enhancements of the Asset Visibility and Supply Viewer modules in Decision Support Tool (DST). These enhancements were directed by Assistant Secretary of the Army (Acquisition,Logistics, and Technology) ASA(ALT), Headquarters Department of the Army and the Army Materiel Command Commanding General approved on the DST 1 to N List. Recommended: LDAC is receiving Unique Item Tracking data daily from DPAS: WE WOULD LIKE TO ADD THESE ADDITIONAL DATA ELEMENTS: Document Identifier Code (DIC)l; Document Number; NSN; Nomenclature; Quantity, LIN; Unit Identification Code (UIC); Unit of Issue; Status Code; Ship to DODAAC; Ship from DODAAC; Estimated Shipment Date; Storage location (SLOC); Ship from RIC; Ship to RIC; Gaining UIC Serial number and Losing UIC. Mission Critical: Army Regulation (AR), AR710-2, AR735-5, AR770-2 par 1-6; par 1-13; Decision Support Tool is the Army's authoritative source for the distribution / redistribution of the allocations to the unit identification code (UIC) level of detail. The DST is the Army's collaborative tool used to synchronize the distribution and redistribution of equipment and materiel in accordance with Army priorities. OPERATION ORDER, 24-231, U.S. Army Materiel Command Implements Auditable Presidential Drawdown Authority Article Transfer Accountability and Tracking Processes Benefits: LDAC will be able to provide advance Asset Visibility of the stocks/assets are being transfered from the DPAS warehouse to the Army New Equipment Fielding Facility (NEFF) site for distribution. This will aid in the coordination synchronization at these NEFF sites for Units receiving new equipment, facilitates training, and prepares vehicles for installation of weapons platform at these facilities prior to hand off. Provides end to end In-Transit Visibility of asset the are in the Supply Chain as required by the Presidential Drawdown Closure of Proposed Sourcing Decisions (PSDs) in DST via DST automated processes. Frequency: Daily Users: DST currently has 64,355 active users. High Priority.
02124	Regional Customer Assistant Role change	Warehouse	USMC	New	Change Request: New Role Design Description: USMC uses the DPAS role Regional Customer Assistant quite frequently, and specific Inquiries are not currently visible to users assigned this role. The Inquiries that appear to be omitted from access include: • Quality Control / Inspection Results Inquiry • Appointment Inquiry • Additional Info Inquiry • Member Feedback Inquiry • Stock Item Inventory Inquiry Recommended: Add the following inquiries to the Regional Customer Assistant role: • Quality Control / Inspection Results Inquiry • Appointment Inquiry • Additional Info Inquiry • Member Feedback Inquiry • Stock Item Inventory Inquiry • Inventory Adjustment Money Value Gain/Loss Inquiry Mission Critical: Adding additional processes to the Regional Customer Assistant role. Benefits: Users with the role will have access to additional processes to perform their job. Frequency: Daily Users: Anyone with the Regional Customer Assistant role.
02123	Manufacturer Part Number	Warehouse,Materiel Management	NAWC WOLF	New	Change Request: Process Improvement Description: Currently the only place that ties the Manufacturer Part Number to the Stock Number is in the Manufacturer Part Nbr table. It does not cross to the inventory records. This causes the users to first search that table to cross part numbers to stock numbers. Recommended: To have the Manufacturer Part number to be added to the inventory record and have it added to the search criteria, inventory reports, and to the grid options. Mission Critical: Benefits: Increased productivity and efficiency of the user. Frequency: Daily Users: At the very minimum 100+ users
02122	Multi line-item Acquisition data form	Materiel Management	NAWC WOLF	New	Change Request: Process Improvement Description: Currently can only and single items with the existing Leidos Single line-item Acquisition data form. After the award of a Government Contract which consists of multiple line items causing increased manual transactions A single contract can have a hundred plus line items. Recommended: To have the capability of uploading multiple line items / CLINS into the MM/ICP module of DPAS, after the award of a Government Contract consisting of multiple line items, which will in-turn create the Due-ins within the WM module. Mission Critical: Benefits: Increased productivity and efficiency of the user. Frequency: Daily Users: At the very minimum 40 users
02121	FLIS Overlay Consumption	PA,MU,Warehouse,Materiel Management,FSM,Registry (SA/LW),Enterprise	Leidos	New	Change Request: Process Improvement Description: Within the last year FLIS has updated their data to a new IDV8 XML format for deltas which DPAS has successfully accomidated and receives daily, however, the monthly data overlays which contain additional NSNs from webFLIS are provided via bar (\|) delimited lst files for which DPAS does not currently have a parser for outside of the one used for the annual surcharge data. Recommended: The DPAS application should be updated to detect these overlay files and consume them into DPAS_FED_LOG consistent with the existing jobs Mission Critical: The requested change is to provide an automated method for processing overlays which will improve the FLIS data for the DPAS customers. Benefits: This change will ensure DPAS is consuming all data provided from webFLIS to ensure greater data consistency between NSNs visible from webFLIS and those loaded into DPAS Frequency: Monthly Users: Application Upgrade
02120	SA/LW DLMS Changes (ADC 1244)	Warehouse,Materiel Management	Leidos	New	Change Request: Process Improvement Description: DoD is modifying how the reporting of SA/LW will be responded. They will be responded through the use of APIs referred to as LLASIE. Once this process is implemented, the DLMS 140A and DLMS 888A transaction sets will be eliminated. The required changes are detailed in ADC 1244 and its addendum's. The elimination of the SA/LW transactions requires several changes to the DLMS changes in reporting receipts, gains, losses and turn-ins. The implementation of LLASIE is covered by DPAS SCR 01988. Recommended: This SCR is to cover the business changes. and the DLMS reporting changes required to comply with DLMS 1244B as it relates to the changes outlined in enclosure 5 - DLMS 856S, 856R, and 947I Mission Critical: The implementation of this SCR will improve materiel activity reporting within the DLMS transactions sets as outlined in ADC 1244B. Benefits: Ensure DPAS maintains DLMS compliant, and provides for additional materiel reporting that enables the elimination of separate SA/LW reporting outside of the standard supply reporting. Frequency: Daily Users: This change impacts all users that manage SA/LW within DPAS
02119	MM Purpose Code Functionality	Warehouse,Materiel Management	USMC	New	Change Request: Process Improvement Description: During the System Acceptance Test (SAT) conducted by MARCORLOGCOM personnel on March 4, 2025, it was discovered that the Purpose Code logic development was done incorrectly and if not corrected will result in a failure point when conducting the MARCORLOGCOM GAP analysis. When an Inventory Control Point (ICP) is being utilized within the ELMS application, full control of assigning the Purpose Code element is to be done by Inventory Managers through use of the Material Management module. Observations during SAT showed the functionality and entry point for Purpose Code was programed to be only accomplished through the Warehouse module. This method of entry should be allowed ONLY when a warehouse DoDAAC is separated from an ICP and is not being managed through the Material Management module. Assignment of the Purpose Code is the inherent responsibility of the Inventory Manager and as such should be accomplished within the Material Management module. Purpose Code is used by the ICP to stratify inventory and is not a warehouse function. This request for modification aligns the business processes required by MARCORLOGCOM WSMC. Recommended: 1. The system shall provide the Inventory Manager with the capability to enter the Purpose Code element from within the Material Management module. This capability will be restricted to Inventory Manager role when the Inventory Control Point (ICP) is utilizing the Material Management module. 2. The system shall be set to NOT allow the Warehouse module to adjust the Purpose Code element when a DoDAAC is assigned to an ICP. 3. When a new due-in is presented for receipt processing at a Remote Storage Activity (RSA) that has been assigned to Inventory Control Point (ICP), an initial Purpose Code assignment of “A” shall be made. It is the responsibility of the Inventory Manger to reassign the Purpose Code to it proper location utilizing the Material Management module not the warehousing module. Note: The reassignment of the Purpose Code is a dynamic process which may require an Inventory Manager to adjust the Purpose Code several times, by serial number over the life cycle of an asset. 4. The ELMS system shall ensure the LQ (Industry Code) “99”, representing Purpose Code, is present in all required DLMS transactions and represents the correct values as entered in the Material Management module. In the case of the 947I “Warehouse Inventory Adjustment Advice” transaction, the W19/AD element must be included identifying a change in Purpose Code assignment. 5. The ELMS system shall ensure all historical transactional records contain the Purpose Code value when assigned. 6. The ELMS system shall ensure the Purpose Code value is available to be selected in search criteria when users are isolating data in inquiries. Mission Critical: MARCORLOGCOM Inventory Management personnel are required to know, at all times, where managed inventory resides within the Purpose Code stratification. Rolls separation between the Warehousing and Material Management, when it pertains to the entry and management of the Purpose Code value is strictly adhered to in MARCORLOGCOM’s business processes. Benefits: • Meets MARCORLOGCOM’s business model. • Provides 100% accountability of assets. • Complies with current audit controls. Frequency: Hourly Users: All system users within the Marine Corps Logistics Command, including Material Managers, Warehouse Managers, and Inventory Control Points, will benefit from these enhancements.
02118	Include Carrier Data in all DLMS 856S/856R/945A Transactions when the shipment involves a commercial carrier	PA,Warehouse,Materiel Management	USMC	New	Change Request: Policy/Regulatory Description: Warehouse Module (WM), When the 945A and the 856S transactions are generated, the N1 (Name) Entity Identifier Code of CA (Carrier) needs to be added to the transactions to identify the type of carrier a shipment has been assigned to for the purpose of tracking shipments (Identified as USMC System GAP ID # 11. The N1 Entity Identifier Code “CA” is missing from the to the outputted 945A and 856S transactions. This element provides additional tracking information to the end user. Recommended: 1. The system shall include the N1 Entity Identifier Code “CA” providing the additional information on the outputted 945A and 856S transactions. Format of required data as prescribed by DLMS is as follows: Transactions Type: 945A and 856S Example: *N1CAARL LOGISTICS2AGQC* N1 : Name qualifier CA: [Entity Identifier Code] representing the carrier used for the shipment 2: [Identification Code Qualifier] “2” identifies the Standard Carrier Code (SCAC) AGQC: Identifies the code represented as specified by the SCAC. Complete listing can be queried using: https://scaccodelookup.com/scac-name-lookup/# Mission Critical: Warehouse Module (WM), When the 945A and the 856S transactions are generated, the N1 (Name) Entity Identifier Code of CA (Carrier) needs to be added to the transactions to identify the type of carrier a shipment has been assigned to for the purpose of tracking shipments. Benefits: • Meets MARCORLOGCOM’s business model. • Provides 100% accountability of assets. • Complies with current audit controls. Frequency: Hourly Users: All system users within the Marine Corps Logistics Command, including Material Managers, Warehouse Managers, and Inventory Control Points, will benefit from these enhancements.
02117	UIC management and Data Masking	PA,Materiel Management	FH-AFHAF	New	Change Request: Policy/Regulatory Description: Currently the user is required to manually update the Unit Kind Code when, UIC name and APO City when a UIC has been designated as a FAD1. The combination of certain data elements potentially change the classification of the UIC, and could potentially cause a security risk or spillage. Additionally, when users run inquires under the 'Asset Inquires' process there is a potential that certain combinations of data elements could pose a risk. Recommended: Establish triggers in place to mask the data when the FAD code for a UIC is inserted or updated to a FAD 1. Additionally establish controls within the system that would limit the combination of data elements that could pose a risk and produce an error notifying the user that there is a security risk. The error should not allow the user to bypass the warning if they do not make any adjustments to the combination of data elements. Potentially move the UIC management process out of the APO/Property Administrator profile and move it all to a SIPR environment fro better controls of access. a. The association of the nomenclature of any single unit or program with the FAD I level designator is classified SECRET. b. Any compilation of forces, units, activities, projects, or programs associated with the FAD I level designator is classified SECRET. Mission Critical: AW CJCSI 4110.01F The Service Chiefs are required to develop and implement policies on the use of and oversight of all FAD codes assigned to units. Security Information – United States Only. Classified lists reflecting authorized FAD I requisitioning entities are distributed and maintained by the Joint Staff Directorate for Logistics, J-4/J-44. This list is distributed on a strict “need-to-know-basis.” DoD components and associated agencies are authorized to determine the appropriate distribution within their organizations following standard security procedures. The following classification guidance applies when information is extracted from the lists: Benefits: Reduces the risk of spillage of sensitive or classified information on unclassified networks. Frequency: Daily Users: Daily files are sent to ADVANA as the DAF Data Repository where users can access information to build reports. Currently there are ~1600 users that have access to DPAS PA that could have access to Master Data information.