System Change Requests

System Change Requests Header

Unlike submitted Support help tickets, System Change Requests (SCR's) can only be submitted through your organization's appointed and authorized DPAS 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 DPAS CCB member representatives or Primary IO are, you may email the DPAS 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.

Enter your SCR Number in the filter below, or click the column title header to sort by that column. You may also download an Excel file of the record data by selecting the blue Excel logo in the upper right corner of this page.

Filter

SCR Number	Title	DPAS Module	Reporting Organization	State	Description
02150	Include PSD Id in TPF Transactions	PA,Materiel Management	ASA-ALT	New	Change Request: Process Improvement Description: The Army's Decision Support Tool (DST) is the system that tracks new equipment fielding and when they are to occur. Each fielding is assigned a PSD Id to each each equipment fielding. Currently the PSD Id is not included in the DLMS transaction to denote why the equipment is being sent to a Unit. The proposed improvement is to have ELMS provide for the input of the PSD Id into the PA Disposition Transfer Out and into the MM Customer Requisition processes enabling the value to be included in the DLMS transactions. See also ELMS SCR 01938 Recommended: 1. Modify MM Customer Requisition to provide for input of the PSD Id. 2. Modify PA Disposition to provide for the input of the PSD Id. 3. Include the PSD Id in the DLMS 527D (PMR) and DLMS 856S (Shipment Status) transactions sets within the Reference Identification loop using the PWC qualifier. Mission Critical: Provides 100% confirmation to DST that the fielding has occurred. Benefits: Provides visibility that a fielding is being planned via the 527D. Provides 100% validation that the planned fielding occurred enabling DST to be able to close the fielding systematically. Frequency: Daily Users: All users that issue/transfer materiel to users of GCSS-Army.
02149	Option to print DD 1348 before disposal is approved	Warehouse	ASA-ALT	New	Change Request: Process Improvement Description: When creating a disposal action within the DPAS WM module a DD 1348 can't be printed until the disposal is approved by the "Warehouse Manager and the "COR". For the COR to approve a disposal action they should verify that all signed documentation is uploaded in DPAS before approving the action. Since the DD 1348 can't be printed until after the COR approves the disposal the users are having to create the DD 1348's outside of DPAS. This can cause issues with data accurate since the users can't allow the system to generate the information. This also increases the time it takes to complete the transaction. Recommended: Allow the DD 1348 to be printed before the COR has to approve the transaction but after the "warehouse manager" has given the first approval. Mission Critical: The process must be flexible to support the business. This change will enable greater flexibility. Benefits: The DD 1348 will no longer have to be created outside of DPAS therefore the time to complete the action will decrease and the data on the DD 1348 will be in sync with the information that has been stored in the DPAS WM module. Frequency: Daily Users: All
02148	DCAPES interface for FSM	FSM	DAF	New	Change Request: Process Improvement Description: Currently Authorization managers must input readiness code 'A' authorizations into FSM either via Mass update or manual input. In some cases the Unit Type Code (UTC)s and Auth details in FSM do not match the UTCs in the authoritative system which causes mismatches between the systems and requires manual intervention. Recommended: Establish an interface to the authoritative system Deliberate and Crisis Action Planning and Execution System (DCAPES) to limit or eliminate manual intervention. The DCAPES PMO also has a requirement for their system to accommodate this requirement Mission Critical: Removes the manual process of establishing readiness code 'A' requirements. Additionally this will resolve a recent AFAA audit finding, that identified mismatches in FSM from the authoritative database with regard to UTC requirements Benefits: By leveraging the direct interface we remove the manual process and remove the requirement to reconcile the data from both systems. Frequency: Daily Users: Existing UTCs are validated biennially, currently there are over 160K UTC tasked authorizations
02147	NSN COG Information	Warehouse	Navy	New	Change Request: Process Improvement Description: Currently the COG information does not import from FLIS nor is there a field for the COG. Recommended: Allow the COG to import from FLIS and add that field to DPAS records. Mission Critical: Benefits: We track the COG for our equipment for reporting purposes. It will allow us to continue that process. Frequency: Daily Users: 100+ Users
02146	Inventory Status	Warehouse	Navy	New	Change Request: Process Improvement Description: There is not a way to track status of an inventory. Recommended: Create an Inventory Status report that shows locations that have been inventoried and those that have not been inventoried for a user selected date range. Mission Critical: Benefits: Allows for a way to track inventoried and to be inventoried locations for a selected date range. Frequency: Daily Users: 100+ Users
02145	PROJECT POC	Warehouse	Navy	New	Change Request: Process Improvement Description: Unable to determine the project POC from the Project table. You can only view it by editing the project code. Recommended: Add the project POC information to the grid options of the project table. Mission Critical: Benefits: Allows the user to view the project POC. Frequency: Daily Users: 100+ Users
02144	Project Field Character Increase	Warehouse	Navy	New	Change Request: Process Improvement Description: Current field is only three characters. With the size of our structure we need to increase the number of characters from three to ten. Recommended: Increase the number of characters from three to ten. Mission Critical: Increasing the Project Code will prevent the duplications of project numbers. Benefits: Increasing the Project Code will prevent the duplications of project numbers. Frequency: Daily Users: 100+ Users Removed 04/29/2025 - per email from Justin Smeltzer - Project Code is a DoD Standard Element
02143	Maint Mgmt Assignment by Custodian Nbr	PA,Materiel Management	USAF	New	Change Request: Process Improvement Description: Current DPAS configuration limits the ability to assign assets to M&U at the UIC level. Aviation maintenance units within FH-AFHAF have custodian accounts that are not required to use M&U but assigned assets are loaded against a Maint Group ID (MGID). This results in asset records being bridged over to M&U but are not actively managed. Recommended: Provide capability to bridge/ unbridge by Custodian Number's. Adding MGID characteristic to Custodian Number's. Mission Critical: PAD 22-02 signed by the Chief of Staff of the Air Force (CSAF) directs the centralized management of CAvSE at the enterprise level, residing within the 440 SCOS Aviation Support Equipment Management Flight. This change will allow for future data mining actions, ensuring equipment accuracy. Benefits: This will enable the Air Force to achieve the desired effects in improving overall readiness and war-fighter support. Frequency: Hourly Users: This change will be applicable to 15,000+ users assigned to Site FH-AFHAF, as well as other agencies or departments that conduct maintenance on their support equipment.
02142	Inclusion of TFSMS Attribute Data in the Enterprise Catalog	PA,MU,Warehouse,Materiel Management	USMC	New	Change Request: New System Process Description: The interface being constructed between TFSMS and ELMS was lacking key attributes that are essential in identifying and defining the LIN/TAMCN used by the Marine Corps. Inventory Managers and Equipment Specialists throughout the Marine Corps rely on the additional data being requested to assist in their day to day management of Class VII inventory. The data being asked for should be added to the Enterprise catalog. Recommended: 1.0 The ELMS system shall include in it interface with the Marine Corps TFSMS system the following key attributes used to minimally assist in identification and defining controlled Class VII inventory: TAMCN NATIONAL_STOCK_NUMBER STANDARDIZATION_CATEGORY_CODE TAM_STATUS TAM_STATUS_DATE ITEM_EXIT_DATE COLLOQUIAL_NAME MODEL_NUMBER DIMENSION_HEIGHT_IN_FEET DIMENSION_WIDTH_IN_INCHES DIMENSION_WIDTH_IN_FEET DIMENSION_LENGTH_IN_FEET DIMENSION_LENGTH_IN_INCHES DIMENSION_HEIGHT_IN_IN STAND_PKG_CUBECHES STD_PKG_LB_WT 1.1 Once the interface is established, the ELMS system shall include all identified attributes in the Enterprise level catalog for the Marine Corps. the primary key to link the information to the catalog is [National_Stock_Number]. 1.2 Once the information is included in the Enterprise level catalog, ELMS will make that information available to sub-catalogs (ie, SKO, Stock Item, M&U, Material Management, PA) 1.3 The frequency of the update shall be dependent on the interface agree established between Marine Corps TFSMS system and ELMS. 2.0 NSN SUBSTITUTION: The ELMS system shall provide the inventory Manager, operating in the Material Management module, with the capability to substitute an NSN within a TAMCN group, taking into consideration STANDARDIZATION_CATEGORY_CODE from the TFSMS attributes, which will be added to the Enterprises Catalog. 2.1 In the case where a denial is received at the Material Management module and the document is placed back into a backorder status. ELMS shall provide the Inventory Manager with a capability to substitute and NSN only when the replacement NSN is with the like LIN\TAMCN group. The criteria for the replacement will be strictly controlled by NSNs that have "In Service" (IS), "Plan Allowance" (PL), Disposal Plan (DP) assets available based on the [TAM_STATUS] attribute in the catalog. 2.1.1 At no time shall the system provide the Inventory Manager with the ability to select and alternate asset that is in Achieve (AR) status. 2.2 At the time of substitution, the Inventory Manager shall be provided with the capability to chose a replacement NSN with a different Condition Code and Purpose Code availability. 2.3 ELMS shall be programed to conduct a virtual verification of the selection being made by the Inventory Manager ensuring the warehouse selected, the NSN, quantity, Condition Code and the Purpose Code and support the requested MRO. If the asset is not available matching the specifications identified for the substitution, ELMS will provide the Inventory Manager with an alert and the process will be halted until the error is corrected. Mission Critical: Benefits: Meets MARCORLOGCOM's business model Assists in 100% accountability of assets Complies with current audit controls Frequency: Daily Users: Affects all USMC users
02141	Inbound Serial Number Enforcement for EDI	Materiel Management	USMC	New	Change Request: New System Process Description: ELMS must enforce Serialized Item Management (SIM) for designated National Item Identification Numbers (NIINs) across various Enterprise Logistics Management System (ELMS) modules. Data exchanges with external trading partner systems via DLMS EDI/X12 transactions sometimes fail to include required serial numbers for serialized assets. This occurs primarily in, but not limited to: • 856S (Shipment Notices – Due-In Transactions) • 945A (Materiel Release – Advice Transactions) • 947I (Inventory Adjustment Transactions) The absence of serial numbers in these transactions compromises data integrity and prevents compliance with DoD serialized property management regulations outlined in: • DoDM 4140.01 (DoD Supply Chain Materiel Management Procedures) • DLMSO Manuals (DLMS Volume 2, Supply) • MILSTRAP/DLMS Mapping for EDI transactions This System Change Request (SCR) proposes a standardized method to detect, report, manage, and resolve these data quality format issues within ELMS. These changes are required to enforce compliance with SIM policies within DPAS modules and ensure accurate logistics accountability and audit readiness. Recommended: Implement an automated edit-check mechanism within ELMS to identify inbound DLMS EDI transactions missing required serial numbers, route them to an error handling interface for user remediation, and support transaction reprocessing once corrected. This ensures serialized assets are tracked consistently across the enterprise. Scope: This change applies to all ELMS modules ingesting DLMS EDI/X12 transactions involving serialized asset movement, including but not limited to: • Receipt and Due-In processing • Inventory management and adjustments • Inbound shipment confirmations • Materiel Release Orders Requirements: 1.1. Edit Checks for Serialized Transactions. ELMS shall implement automated validation logic for inbound EDI 856S, 945A, and 947I transactions to detect when a transaction line item is for a NIIN that is marked as serialized but lacks an associated serial number(s). 1.1.2 Enforcement Against Serialized NIIN Catalog. The system shall reference the ELMS NIIN Catalog or Master Item File to determine if an item requires serialized tracking before enforcing serial number validation. 1.1.3. Transaction Error Flagging. Transactions missing required serial numbers shall not be ingested into ELMS records but instead flagged as “Unprocessed” and queued for user intervention in the Interface Queue Manager. 1.1.4. Error Queue Management Dashboard. ELMS shall provide an enhanced dashboard view in the Interface Queue Manager that displays: • Transaction type (i.e., 856S, 945A, 947I, etc.) • Originating trading partner • NIIN and quantity • Serial number missing status • Error message: “Serialized NIIN reported without corresponding serial numbers” 1.1.5. Manual Update Interface. The dashboard shall support manual entry of missing serial numbers by the ELMS User after collection from the originating trading partner system. 1.1.6 Audit Trail Capture. The system shall capture all entries made manually to enhance the inbound EDI transactions: • User ID • Date/time stamp • Action performed • Original vs. updated values 1.1.7 Reprocessing Capability. Once updated with the required serial numbers, the transaction shall be made available for resubmission ingestion using standard processing logic. Successful ingestion will update the transaction status to “Processed” and remove it from the error queue. 1.1.8 System Alerts. ELMS shall provide automated notifications (email or in-system alert) to designated user roles when transactions are flagged as unprocessed due to missing serial numbers. 1.1.9 Metrics and Reporting. The system shall generate periodic reports that include: • Number of transactions flagged for missing serials • Time to resolution • Frequency by trading partner • NIINs most affected 1.1.10. Configuration Flexibility. Administrators shall be able to update the list of NIINs subject to Serialized Item Management without requiring code changes, using an ELMS catalog or configuration table. Mission Critical: Benefits: Meets MARCORLOGCOM's business model Assists in 100% accountability of assets Complies with current audit controls Frequency: Daily Users:
02140	Upload of Supporting Documentation to Documents that are Closed	PA,Warehouse,Materiel Management	USMC	New	Change Request: New System Process Description: ELMS currently does not possess the ability to attach Key Supporting Documents (KSA) (ie. LTI's, signed 1348s, 1149) to a document that is in a closed status. This was discussed during the on site visit to the ELMS LEIDO's facility in early March 2025. This will impact MARCORLOGCOM's ability to answer audit related inquires if not resolved. Recommended: 1.0 Inventory Managers, using the Material Management (MM) module, shall be provided with the capability to upload an attached Key Supporting Documentation (KSDs) to documents considered closed in ELMS. This is to facility the requirement to extract supporting documentation during an audit evaluation. 1.1 ELMS shall provide the Inventory Manager, the Material Management (MM) module with a capability retrieve attachments from any document recorded in the system. 2.0 Warehouse personnel, using the Warehouse Module (WM) module, shall be provided with the capability to upload an attached Key Supporting Documentation (KSDs) to documents considered closed in ELMS. This is to facility the requirement to extract supporting documentation during an audit evaluation. 2.1 ELMS shall provide warehouse personnel, in the Warehouse Module (WM) module with a capability retrieve attachments associated to the warehouse they are assigned to. 3.0 Personnel using the Property Accountability (PA) module, shall be provided with the capability to upload an attached Key Supporting Documentation (KSDs) to documents considered closed in ELMS. This is to facility the requirement to extract supporting documentation during an audit evaluation. 3.1 ELMS shall provide personnel using the Property Accountability (PA) module with a capability retrieve attachments associated to the account which they are assigned to. Mission Critical: Benefits: Meets MARCORLOGCOM's business model Assists in 100% accountability of assets Complies with current audit controls Frequency: Daily Users: This change impacts all USMC users
02139	Warehouse Financial Accounting	Warehouse,Materiel Management	MDA	New	Change Request: Process Improvement Description: MDA has a requirement to manage operating materiel and supplies "OM&S" that are currently being managed using MS Excel spreadsheets. In addition, MDA is requesting DPAS system enhancements to support “actual cost” accounting for OM&S within the warehouse module. On occasion, MDA may have assets (non-capital and capital) that are awaiting transfer / disposition that it would like to have stored in a warehouse. DPAS does not currently support fixed asset accounting or OM&S accounting by actual cost for items that are accounted for in the warehouse. The proposed solution is for DPAS to configure to manage fixed assets within the warehouse module or through integration with a fixed asset module and to be able to electronically report those items to the MDA financial statements supported by Defense Agencies Initiative (DAI). Recommended: • By Stock Nbr, permit the user to determine how they want to financially account for the $ value of OM&S (MAC, LAC, ACT). Note: MAC = Moving Average Cost, LAC = Latest Acquisition Cost and ACT = Actual Cost. Actual cost would be limited to serialized OM&S. • Develop a DAI accounting interface reporting capability to report capital assets and OM&S managed within the warehouse similar to how property accountability performs the financial reporting. • Enable fixed assets and OM&S to transfer between DPAS modules along with their cost and depreciation. Items transferred between organizations with different catalogs will need to have the valuation set based upon the receiving entity's catalog. Mission Critical: The implementation of this SCR is in support of customers of the Warehouse / Materiel Mgmt. modules in support of financial accounting of fixed capital assets and OM&S. Methodologies must be DoD 7000.14R / FASAB / US. Treasury USSGL compliant to support an agency's Financial Improvement Audit Readiness "FIAR". Benefits: Supports financial compliance for all assets / supplies accounted for using DPAS regardless of module. Frequency: Daily Users: This change impacts all users of the Warehouse module.
02138	Update DRRS reporting for DAF Site-ids	PA,MU,Warehouse,FSM	HQ AF/A4LR	New	Change Request: Policy/Regulatory Description: With the implementation of SCR 1935, we now require an updated Defense Readiness Reporting System (DRRS) report that will include the Authorization identification code on the property record. Additionally now the the Aviation Support (AvSE) community has completed the implementation of the M&U module we will also need to include the status of the assets that have been profiled in M&U. Recommended: Recommend updating the current DRRS report to include all DAF assets and add in the new data elements that are required for reporting Mission Critical: IAW CJCSI 3401.02B Services are mandated to report DRRS readiness capabilities Benefits: DAF will be in compliance with CJCSI 3401.02B Frequency: Weekly Users:
02137	MRP 870M / FTR FTZ response to 180M/FTE -1b	Warehouse,Materiel Management	USMC	New	Change Request: Process Improvement Description: From MARCORLOGCOM's initial walk-thru in ELMS on the Material Returns Program (MRP) processes, it does not appear the system is in compliance with DoD policy as it relates to the appropriate response to a report of excess. This BRD is to clarify and levee a more comprehensive requirement to ensure the system is providing the necessary information to the Inventory Manager, in the Material Management Module (MM/ICP) to respond to the DLMS 180M/FTE report of excess. Recommended: 1.0 Material Management (ICP) module required changes to respond to incoming Material Returns Program (MRP) DLMS180M/FTE DLMS transactions in accordance with DLM 4400.25 Vol 2 Chapter 11 (see attachment) 1.1 The ELMS system shall intake all incoming 180M MRP transitions, from DAAS, and route them to the appropriate Owning-RIC also known as the Primary Issue Control Activity (PICA) within the Material Management (MM) module. 1.1.1 Once the 180M transaction has been inbound within the proper ICP management area, in Material Management, the system shall assigned the work to the appropriated Inventory Manager designated by the association of the NSN to the [Program Name]. 1.1.2 The system shall provide the Inventory Manager with the capability to respond back to the 180M with the appropriate 870M/FTR transactional response. (see attachment for appropriate response codes) 1.1.3 The system shall provide the Inventory Manager with a set of values representing the FTR response statuses for selection during the 870M transaction build. (See MRP Process Flow attachment) 1.1.3.1 If the Inventory Manager responds with any Status codes begin with "S" (Rejected) the system will created and respond back to the originator via DAAS with an (870M, LQ0FTR, LQ81S_) noting the selected Status code. 1.1.3.1.2 If the Inventory Manager responds with any Status codes begin with "S" (Rejected), following the transmission of the 870M response, the system will mark the transaction as closed, no further action required. (example of DLMS X12 870M transactions attached) 1.1.3.2 If the Inventory Manager responds with Status codes [TA, TB, TH, TJ] the system will created and respond back to the originator, via DAAS with an (870M, LQ0FTR, LQ81T_) noting the selected Status code. The 870M will remain open until the equipment is received or the 180M cancellation is received by the originator. 1.1.3.2.1 The system shall provide the Inventory Manager with the ability to Identify the location the equipment will be shipped to ( example: N1STM4BR4) and the PICA or Owning RIC the asset will be managed by (N1Z8M4MPT). 1.1.3.2.2 The system shall produce a 527D (Due-in/Advance Receipt) notification also known as the Preposition Material Receipt (PMR) directed to the receiving storage point and Owning-RIC as directed in the 870M. 1.1.4 If the system receives a 180M / FTC (Cancellation Request) the original document will be marked closed and retired in ELMS. 2.0 The Warehouse Module (WM) will be prepared to receive the inbound due-in transactions as directed by the 527D PMR. 2.1 The system shall possess the capability to receive 870M/FTL and 856R/FTM transactions coming for the originator via DAAS as directed in the aforementioned 870M/FTR response. 2.1.1 The system shall provide the Inventory Manager, using the Material Management (ICP) module and the receiving warehouse person using the Warehouse Module (WM) with the ability to see all transactions relating to MRP. 2.1.2 The system shall provide the receiving warehouse with a capability to receipt for the inbound shipment using the designated 870M/ FTZ transactions with the appropriate status codes. (See MRP Process Flow attachment) 2.1.2.1 If the shipment is received and all assets are accounted for, the WM module will produce the 870M/FTZ transactions that will be transmitted back to the Owning RIC/ICP via DAAS. 2.1.2.2 The receiving ICP, using the Material Management/ICP module, shall verify the transactions document received and mark the MRP transaction as closed. The 870M/FTZ will record the appropriate elements (870M, LQ0FTR, LQ81T_) noting the selected Status code. Mission Critical: Benefits: Meets MARCORLOGCOM's business model Assists in 100% accountability of assets Complies with current audit controls Frequency: Daily Users: All users with Material Managers, WH Managers, ICP and all USMC users
02136	Changes to SKO Screens - 1b	Warehouse,Materiel Management	USMC	New	Change Request: Compliance Requirement Description: During MARCORLOGCOM's evaluation of the Set, Kit, and Outfit (SKO) capability, it was observed that in several location in the process the LIN/TAMCN and or National Stock Number (NSN) of the Parent were missing in search grids and component grids. In addition, the Marine Corps is requesting the ability to add a component type when adding associations for the parent to its components. Recommended: 1.0 "ICN Inventory Update Inquiry" when selecting the components of a Parent NSN, the system does not display the Parent NSN nor Parent LIN/TAMCN in the SKO summary view. The following requirements are required to gain the required functionality associated with WSMC business processes. 1.1 On the "Inventory Update Inquiry", after selecting a specific serial number known to have a TAMCN, the component Grid did not contain the Parent LIN/TAMCM or the Parent NSN. The system shall be modified to display the Parent LIN/TAMCM and the Parent NSN on the SKO summary view. (see attachment) 1.2 The system shall add ‘Component Type’ drop down containing the below value set on the ‘Component’ tab of the "SKO" Add screen. (see attachment) a. SSRI (child) b. SL3 c. SL4 d. DLR e. Collateral Material 1.2.1 The system shall add the "Component Type" to all search criteria associated to SKO. 1.3 The system shall provide the end user with a capability to search by LIN/TAMCN, This functionality is currently missing from the SKO Add screen. (see attachment) 1.4 The system shall add a criteria for the end user to be able to search by LIN/TAMCN on the “SKO Catalog Landing Page” 1.5 The system shall add a criteria for the end user to be able to search by LIN/TAMCN on the “SKO Catalog Landing Page” Options selection. 1.6 In the “ICN Inquiry” add ‘Component Type’ drop down containing the below value set as a ‘Search Criteria’ Field to the ICN Inquiry Landing Page: a. SSRI (child) b. SL3 c. SL4 d. DLR e. Collateral Material 1.7 On the “SKO Assembly Process Screen”, the system shall add LIN/TAMCN as a default grid option and a search criteria option. (see attachment) 1.8 On the "Kit Assemble" screen, when selecting serial number in the search criteria, the system shall be modified to display the Parent LIN/TAMCN. 1.9 On the "Kit Assemble" screen, when selecting serial number in the search criteria, the system shall be modified to display the Parent LIN/TAMCN in the Kit Details area. Mission Critical: This is a critical 1.b requirement that must be satisfied prior to MARCORLOGCOM's implementation. Benefits: Meets MARCORLOGCOM's business model Assists in 100% accountability of assets Complies with current audit controls Frequency: Daily Users:
02135	Assignment of Orphan Status and Shipping Translations - 1b	Warehouse,Materiel Management	USMC	New	Change Request: Process Improvement Description: Currently, it has been observed in ELMS that when Status and Shipping notifications (870S, 856S, 870M/FTL, and 856R/FTM) DLMS transactions are received and there is no due-in present, the intended ICP nor warehouse has the inbound shipment recorded in the system as due in to their location. In short, the transaction exceptions out and no further action is done in ELMS to allow visibility of these transactions without manually hunting them down. This lends itself to frustrated shipments. Recommended: 1.0 Requirements for dealing with intransit transactions transmitted by DAAS where there are missing due-in leading header transactions records. 1.1 When and inbound transactions indicates an Owning-RIC tied to and ICP within ELMS (MPT) or is intended for one of the Remote Storage Locations (RSAs) connected to an ICP, ELMS shall automatically generate a 527D/DWZ (Preposition Material Receipt (PMR)) record for all inbound DLMS transactions (870S, 856S, 870M/FTL, and 856R/FTM) That does not have a due-in resident in ELMS. 1.1.1 If the inbound transactions has a REF/SE or REF/U3 segment populated identifying serial numbers or IUID. the ELMS system shall record that information as part of the due-in record. 1.1.2 The newly established due-in and follow-on status should be recorded at the Material Management (ICP) level and on the document control records of the intended receiving warehouse as an intransit due-in. 1.1.3 If the NSN identified on the inbound transactions is not loaded to the Stock Item catalog of the RSA where the asset has been shipped to, and the NSN resides on the Enterprise LP catalog, ELMS will automatically load the NSN to the Stock Item catalog for that RSA. 1.2 Upon receipt, ELMS shall record the document as a 527R/D6Z showing that the document was receipted for from a document that had NO due-in recorded. 1.2.1 ELMS shall allow all KSDs to be attached to the document in support of audit requirements. 1.2.2 ELMS shall provide a capability to access and retrieve the completed document both from the Material Management (MM) module and the Warehouse Module (WM). 1.2.3 At the same time ELMS produces the 527R/D6Z DLMS transactions it shall also produce the required 527R/DRA and transmit it back to the originator of the shipment. 2.0 If a 527R/D6_ is received from an external storage point, the system shall build the corresponding 527D/DW_ (Preposition Material Receipt (PMR)) record and allow for the posting of the receipt under the Material Management (MM) module under the associated ICP. Mission Critical: Benefits: Meets MARCORLOGCOM's business model Assists in 100% accountability of assets Complies with current audit controls Frequency: Daily Users: All users with Material Managers, WH Managers, and ICP users
02134	Filtering Process for PIEE WAWF Receipt Transactions	PA,Warehouse,Materiel Management	Leidos	New	Change Request: New System Process Description: The setup of PIEE WAWF for the ELMS user must be performed within PIEE. 1) Often times the APO doesn't know who their WAWF coordinator is, 2) the setup isn't specific enough to prevent non-property book receipts from passing to ELMS causing review / deletion of unwanted Due Ins, and/or 3) it requires constant WAWF configuration maintenance between the Accountable Property Officer (APO), and their WAWF coordinator to tweak the WAWF setting in an attempt to receive the desired receipts. Recommended: Create a WAWF filter process on the ELMS side that will provide the APO a filtering process to filter in / out receipts they want to see as Due Ins in PA and/or Warehouse. Once in place, ELMS will enable 100% of the organization's WAWF receipts to flow to ELMS using the ELMS WAWF filtering rules established by the APO to determine which receipts will become a Due In. ELMS will also provide the APO with a view of those receipts that were filtered out and allowing the user select ones that should have created a Due In to be processed into a Due In. Mission Critical: This change incorporates additional PIEE WAWF functionality within ELMS. Benefits: This change will provide improved integration between PIEE GFP and ELMS (APSR). Frequency: Daily Users: All ELMS users that use the PIEE WAWF interface.
02133	PIEE GFP Business Process Improvements	PA,Warehouse,Materiel Management	Leidos	New	Change Request: New System Process Description: PIEE GFP is adding functionality that will enable it to report to the material owner's Accountable Property System of Record (APSR) such as condition code changes and disposition actions via the DLMS 947I Inventory Adjustment Transaction Set. See DEDSO's website for the DLMS 947I Implementation Convention. Recommended: Modify ELMS to accept the DLMS 947I from PIEE GFP and update / remove the material from DPAS. This change will require locating the item in ELMS (PA, WM or MM) and performing the action plus all sub actions to include reporting the financial change should item be financially reportable. Mission Critical: This change incorporates the additional PIEE GFP functionality within ELMS. Benefits: This change will provide improved integration between PIEE GFP and ELMS (APSR). Frequency: Daily Users: All ELMS user with GFP.
02132	Intransit Document Review and Verification - 1b	Materiel Management	USMC	New	Change Request: Process Improvement Description: Current ELMS processes do not provide the end user with serial number detail within the In-Transit Review process to search for and close intransit shipments with an approval process. When documents are sent to an outside entity that cannot reply transactionally confirming receipt of a shipment, it is the responsibility of the Inventory Manager, when Material Management (ICP) module is being utilized, to close out the intransit record once the Key Supporting Document (KSD) is supplied. The in-transit review process will need to have serial number detail to facilitate the processing and closeout of shipments. Serial number level details are specifically needed for instances where the confirmation quantity does not match the shipment information (Either with KSD or Responses that are short). Recommended: The ELMS system shall be enhanced to include a serial number search capability within the “Intransit Review” screen, allowing users to locate and verify specific intransit records. Upon selection of a shipment, all associated serial numbers will be displayed, automatically checked upon first entry. Users will have the ability to uncheck serial numbers not verified as received based on the Key Supporting Document (KSD). A new Stage Code “DS – Discrepant Shipment” is requested to flag and clearly display discrepant serial numbers or quantities. This is a critical enhancement, as current functionality lacks the capability to drill down by serial number for intransit shipment verification and closeout. This feature is necessary to enable Inventory Managers using the ICP module to validate and close shipments when transactional confirmation is not available, ensuring compliance with audit standards. Refer to the attached USMC BRD for additional detail. Mission Critical: This process allows the user to properly adjudicate and confirm in transit shipments, when the receiving agency does not confirm receipt, or confirms receipt with errors or discrepant quantities. Benefits: -Meets MARCORLOGCOM’s business model. -Ensures the accurate closeout of in-transit shipments based on Key Supporting Documents received at external RSA's, DLA-DS, or other entities that do not respond appropriately via DLMS Transactions. Frequency: Daily Users: This SCR will support all users of DPAS Material Management, and clean up an issue with the validation of serialized assets when the quantities do not match between what was shipped and the KSD Received.
02131	TAC Code AUD Table - 1b	PA,Warehouse,Materiel Management,Enterprise	USMC	New	Change Request: Process Improvement Description: ELMS currently does not allow for Transportation Account Codes (TAC) value set to be added to, updated, or values deleted from within the Material Management (MM) module. Inventory Manager (IMs) are often provided TAC codes to be used when redistributing inventory to other services or other entities from within the Marine Corps. The ability to add, update, and delete TAC codes is inherently the responsibility of the IMs using the Material Management module. Recommended: The ELMS Material Management (ICP) module shall enable Inventory Managers to Add, Update, and Delete Transportation Account Codes (TACs) within a controlled value set. Once valid TACs are available, managers can select a TAC when generating a 940R Material Release, which will be embedded in the transaction (segment N9, code "TH") and transmitted to the appropriate Remote Storage Activity (RSA) for further distribution. TAC control remains with the ICP when warehouses are linked. Refer to the attached BRD for additional details. Mission Critical: This process improvement is to allow for the USMC Enterprise Help Desk to make quick updates to the TAC Code to support emerging mission requirements. The DPAS Support help desk ticket to add a TAC Code has been determined pose risks to MARCORLOGCOM Weapon System Managers meeting mission timelines, and hence a User Update Process for this field is required. Benefits: -Meets MARCORLOGCOM’s business model. -Ensures timely processing of shipments in support of Global Force Management and Contingency requirements, that require the quick update of TAC Codes. -Ensures Accuracy of TAC Code Submissions to support interface with DLA Transportation Systems. Frequency: Daily Users: All MARCORLOGCOM Material Managers, and other DPAS Users who will use this process.
Page 1 of 80 Display of 1589 1 2 3 4 ... 6 7 8 9 10