Effective Date: 2024-03-08
This release includes System Change Requests and corrects program deficiencies identified by the user community. Please review the feature and bug list below for a full listing of changes in this release.
System Changes
Accounting
Property Accountability
Helpdesk Tickets / Bugs Fixed
| Ticket Nbr | Module | Details |
|---|---|---|
| 99768 | ICP | LPMAR04 - CFO Accounting Detail Report - AF CMP GFP: 947I transactions with FQ series doc numbers appearing in CFO reports There are incorrect transactions showing in the Chief Financial Officer (CFO) reports. Resolution: When a Condition Code change is initiated from the warehouse, the Inventory Transaction Record of the new Condition Code should have the original MAC value, which is the same as the original Condition Code and not zero.
|
| 102042 | ICP | LPRMN01 - Requisition - PA Requisition - Send 527R TH to SOS when Requisition is received The Property Accountability Requisition is sending the 527R TH to SOS when a Requisition is received. Resolution: The location where the Outbound Records for the 527R TH transactions are written is changed, and now shows up in the Defense Logistics Management Standards Transaction Viewer. This is for Property Accountability receipts only.
|
| 103185 | Maintenance & Utilization | WPMAN10 - VSCOS: MAM Mass Edit AWD error in FFDZV0/341 LRS There is a Maintenance Asset Master Awaiting Disposition (AWD) error. Resolution: A warning is added to the Maintenance Asset Master Add/Update/Delete when Awaiting Disposition (AWD) and Non-AWD Maintenance Management Code assets are selected for edit. The warning states the user cannot edit AWD and Non-AWD assets together.
|
| 103708 | Maintenance & Utilization | WPMAN45 - Asset Assignment Asset ID tab not populating with data The Asset Assignment Asset Identifier tab is not populating with data. Resolution: The Asset Assignment Asset Identifier and Maintenance Schedule Identifier tabs are now populating the data correctly.
|
| 103146 | Maintenance & Utilization | WPMAQ10 - AvSE: 'Originating System' field option add request for M&U Maint Asset Inquiry The 'Originating System' field option is requested for the Maintenance and Utilization Maintenance Asset Inquiry. Resolution: The Originating System field is showing in the Maintenance Asset Inquiry dropdown field, in Field lists, and is in alphabetical order.
|
| 94305, 96505 | Maintenance & Utilization | WPMAQ10 - Cost Center Incorrect FF2HQ0 Cost Centers are not correct in the Maintenance and Utilization Asset Inquiry. Resolution: The Search Results now display the correct Cost Center.
|
| 101330 | Maintenance & Utilization | WPMAQ10 - Data pull request - VSCOS: M&U MAM inquiry data pull with unavailable field data request There is a request in the Maintenance and Utilization Maintenance Asset Inquiry to make specific columns available. Resolution: The new field data is now pulled from the Maintenance Asset Inquiry.
|
| 101330 | Maintenance & Utilization | WPMAQ10 - Missing "Vehicle Assign Type Cd" The Vehicle Assign Type Code is missing on the Maintenance Asset Inquiry. Resolution: The Maintenance Asset Inquiry Search Criteria now has the field "Vehicle Assign Type Code".
|
| 103306 | Property Accountability | WPHRN71 - Reconcile Inventory Data - User is trying to reconcile an inventory and gets an error message: A Reconcile Inventory Error appears inappropriately. Resolution: The Inventory Reconciliation Location field now accepts dashes.
|
| 102287 | Warehouse | Add Consumption Report to 9022 - WH Manager Role (NSWC 102287) The Consumption Report needs to be added to the Warehouse Manager Role. Resolution: The Consumption Report is now available to users with the Warehouse Manager role.
|
| 95220 | Warehouse | LPCTI13 - Condition Cd Recalculation / LPWHN52 - Inventory Update Manager (CSP) / 83 error in Re-Identify attempt in CLJ UIF CBRN (CSP 95220) There is an 83 error when attempting to Re-Identify while using the Inventory Update Manager. Resolution: The error message is updated for clarity.
|
System Change Details
Accounting
01967 - Add Major Command Cd and Agency Cd Fields to ICP Management Screen, Managed DoDAAC tab
Module: Accounting
What Changed:
In preparation for the upcoming Accounting functionality and upcoming changes to the Appropriation Add/Update/Delete (AUD) process in the Materiel Management/Inventory Control Point (MM/ICP) module, the Agency Code and Major Command Code are added to the 'ICP Management' screen on the 'Managed DoDAAC' tab. Users are able to add an appropriation Fund Code, Agency Code, and Major Command Code after the ICP Managed Code is associated to an Remote Storage Activity (RSA), making it an "Owning" Department of Defense Activity Address Code (DoDAAC). Because the Fund Code, Agency Code, and Major Command Code are only available after the DoDAAC is associated to the RSA, those fields are only available for use during the Edit mode of the ICP Management DoDAAC screen. When a Fund Code is selected, the Agency Code and Major Command Code are required.
Roles required are the same for those that currently have access to the Update ICP Management screen.
The Originating Problem:
The existing functionality of the Major Command Code on the Materiel Management Appropriation Add/Update/Delete screen is incorrect for Defense Property Accountability System (DPAS) Accounting.
Impact:
Users are able to associate the Agency Code and Major Command Code to the Owning DoDAAC in the Materiel Management module.
Property Accountability
01931 - Protective Service data elements on DD Form 1348
Module: Property Accountability
What Changed:
The Controlled Inventory Item Code (CIIC) and Demilitarization (DEMIL) Code is added to Block 27 on the Form DD1348.
The Department of the Air Force (DAF) transportation community must be cognizant of the combination of the Controlled Inventory Item Code (CIIC) and Demilitarization (DEMIL) Code to determine if the cargo requires additional messages when transporting property and material. They want the information populated in Block 27 for ease of determining additional precautions.
No impact to the user should be observed.
