Effective Date: 2025-03-21
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
Admin
DLMS
Inventory
Materiel Management
- 01970 - Exclude Allocated Inventory From MM Inventory Selection
- 02100 - Customer Requisition - Add TAC to Customer Requisition/RDO/DRO
Property Accountability
Warehouse
- 02087 - Add Purpose Code / AIT Materiel Movement
- 02087 - Add Purpose Code / Inventory Activity Inquiry (ETL)
- 02087 - Add Purpose Code / Issue & Return processes
- 02087 - Add Purpose Code / Warehouse Disposition
- 02087 - Add Purpose Code / Warehouse Transfer
- 02100 - Warehouse MRO / TAC Updates
Helpdesk Tickets / Bugs Fixed
| Ticket Nbr | Module | Details |
|---|---|---|
| 121266 | Force Systems Management | WPFMQ08 - USAF A4/HAF: FSM Inquiry Export Error There is a Force Systems Management (FSM) Inquiry Export error. Resolution: The issue where exporting in FSM caused an error when using Date-Time search criteria is fixed. Export now functions as expected for all search criteria and does not produce an error.
|
| 122540, 122953 | Maintenance | WPMAN12 - USAF AvSE: WO access/error issues in New Orleans ANG The Air National Guard (ANG) encountered Work Order access/error issues. Resolution: Work orders with any date/time falling on the second Sunday in March, between 2:00 AM and 2:59 AM, no longer encounters any errors during edits or updates on whatever day Daylight Savings Time occurs.
|
| 120355 | Materiel Management | LPRMN01 - Requisition - Technical Order Number field only allows numbers within MU. The Technical Number field only allows numbers. Resolution: The Technical Order Number field now allows alphanumeric characters and dashes.
|
| 119660 | Property Accountability | WPHRQ01 - NSWC: PA Inventory Header inquiry click for Detail view not functioning The Property Accountability (PA) Inventory Header Inquiry click for Detail View is not functioning. Resolution: The issue that prevented users from opening the Inventory Header Inquiry Detail in the Inquiry is corrected.
|
| 123124 | Warehouse | LCDBD01 - DPAS Database / Agency Purpose Code Request (USSOCOM 123124) Load the United States Special Operations Command (USSOCOM)'s Purpose Code values. Resolution: The Purpose Codes are ready for USSOCOM.
|
| 123200 | Warehouse | LPWHN73 - Issue (Warehouse) - Allocation Error on Warehouse Issue w/ Purpose Code There is an Allocation error on Warehouse Issue with Purpose Code. Resolution: In Warehouse Issue, the Purpose Code (Cd), Manufacturer Lot (Mfr Lot), and Contract now apply to the Bulk Asset Allocation record.
|
System Change Details
Admin
02087 - Add Purpose Code / Admin Catalog Management Code Updates
Module: Admin
What Changed:
Purpose code is an optional attribute of the asset record. The Management Code scripts have changed to account for this addition.
DPAS does not currently support segregating materiel in its Materiel Management/Inventory Control Point (MM/ICP) or Warehouse applications by Purpose Code.
Impact:
The Purpose Code in the result is now the same as the Purpose Code from the original request.
DLMS
02087 - Add Purpose Code / DLMS (527D, 527R, 940R, 947I, 867I)
Module: DLMS
What Changed:
The following Defense Logistics Management Standards (DLMS) transactions now support the Purpose Code and are able to report it: 527R, 940R, 947I, and 867I.
The Originating Problem:
DPAS does not currently support segregating materiel in its Materiel Management/Inventory Control Point (MM/ICP) or Warehouse applications by Purpose Code. Previously the 527R, 940R, 947I an 867I DLMS transactions did not report the Purpose Code.
Impact:
The 527R, 940R, 947I and 867I now contains Purpose Code information, via the Industry Code qualifier '99' in each transaction.
Inventory
02087 - Add Purpose Code / AIT Physical Inventory
Module: Inventory
What Changed:
Purpose Code is an optional attribute of any asset record. It is added to the information downloaded to the AIT device, as well as into the upload and resolution processes.
We have made it visible (when set) within the AIT Physical Inventory process.
The Originating Problem:
DPAS does not currently support segregating materiel in the Materiel Management/Inventory Control Point (MM/ICP) or Warehouse applications by Purpose Code.
Impact:
The Purpose Code is visible within the Physical Inventory, Resolution, Export Template and Import processes.
Materiel Management
01970 - Exclude Allocated Inventory From MM Inventory Selection
Module: Materiel Management
What Changed:When creating an Materiel Release Order (MRO), the available quantity for each Remote Storage Activity (RSA) is available and better informed decisions are made as to where the inventory is shipping from.
The Originating Problem:
Choosing an RSA with very little available quantity was common because the total inventory did not account for those items already allocated.
Impact:
The quantity within RSAs is now available.
02100 - Customer Requisition - Add TAC to Customer Requisition/RDO/DRO
Module: Materiel Management
What Changed:It is now possible to choose the Transportation Account Code (TAC) when the Materiel Release Order (MRO) is created.
The Originating Problem:
The ability to choose the TAC before the MRO is generated is required.
Impact:
Choose the TAC when the MRO is created.
Property Accountability
01978 - Non-Serialized WAWF AS Receipts
Module: Property Accountability
What Changed:
An option is added to the background of the Wide Area Work Flow (WAWF) Shipment Advice (AS) job to allow opting in to receiving transactions that do not contain a Unique Item Identifier (UII). If the decision is made to not opt in, then the WAWF AS functions the same as before.
DPAS rejects any WAWF AS transactions that do not have a UII. This results in a note that says "No UII Line Item Exists" in the History Remarks.
Designate that these transactions without UIIs are preferred by informing the Help Desk to change the system setting for their Unit Identification Code (UIC), allowing these transactions (either bulk or serialized assets) into the WAWF AS Pending Transactions screen.
02117 - UIC management and Data Masking - Phase I
Module: Property Accountability
What Changed:
A systematic method is provided to mask specific fields upon selecting a Force Activity Designator (FAD) 1. The Air Force (USAF) has a requirement to mask the Unit Identification Code (UIC) Name, Organization Identifier (Org Id), and Unit Kind Code when FAD 1 is selected. A pop-up displays, asking if the UIC Name should be masked for the other organizations.
The Originating Problem:
Combining certain data elements together caused data to be classified which then affected another system outside of Defense Property Accountability System (DPAS).
All USAF members now receive a new pop-up regarding other organizations.
Warehouse
02087 - Add Purpose Code / AIT Materiel Movement
Module: Warehouse
What Changed:
Purpose Code is an optional attribute of any asset record. It is added to the information downloaded to the AIT device, as well as into the upload and resolution processes.
The Originating Problem:
DPAS does not currently support segregating materiel in the Materiel Management/Inventory Control Point (MM/ICP) or Warehouse applications by Purpose Code.
Impact:
Purpose Code is propagated, with the asset information, during the AIT Materiel Movement process.
02087 - Add Purpose Code / Inventory Activity Inquiry (ETL)
Module: Warehouse
What Changed:
The Purpose Code field is added to the grid for Inventory Changes under the Inventory Activity. Changes to the Purpose Code through Inventory Update or other processes now reflects in the inquiry as a change for assets with the appropriate reason code.
DPAS does not currently support segregating materiel in its Materiel Management/Inventory Control Point (MM/ICP) or Warehouse applications by Purpose Code.
Impact:
Purpose Code changes are tracked within the Inventory Activity Inquiry.
02087 - Add Purpose Code / Issue & Return processes
Module: Warehouse
What Changed:
The Purpose Code is an optional attribute of any asset record. It is added as an optional field in the Issue and Return processes. However, it cannot be changed through them - the Inventory Update process is used.
The Originating Problem:
Impact:
The Individual and Unit Issues and Return processes allow for assets with a Purpose Code to be issued, viewed in outstanding inventory, and returned to inventory.
02087 - Add Purpose Code / Warehouse Disposition
Module: Warehouse
02087 - Add Purpose Code / Warehouse Disposition
What Changed:
The Disposition process now allows Inventory selection by Purpose Code, and it shows where appropriate on screens and grids.Defense Logistics Management Standards (DLMS) transactions out of Disposition (945A and 867I) contain Purpose Codes when available.
The Originating Problem:
Defense Property Accountability System (DPAS) does not currently support segregating materiel in its Materiel Management/Inventory Control Point (MM/ICP) or Warehouse applications by Purpose Code.
Impact:
Disposition allows Inventory selection by Purpose Codes, and shows on appropriate screens and grids.
02087 - Add Purpose Code / Warehouse Transfer
Module: Warehouse
What Changed:
The Warehouse Transfer process now allows for Inventory selection by Purpose Code, and it shows where appropriate on screens and grids.Defense Logistics Management Standards (DLMS) transactions out of Warehouse Transfer (945A and 867I) contain Purpose Codes when available.
The Originating Problem:
DPAS does not currently support segregating materiel in its Materiel Management/Inventory Control Point (MM/ICP) or Warehouse applications by Purpose Code.
Impact:
Warehouse Transfer allows Inventory selection by Purpose Codes, and shows on appropriate screens and grids.
02100 - Warehouse MRO / TAC Updates
Module: Warehouse
What Changed:
The Materiel Release Order (MRO) now processes the Transportation Account Code (TAC) field from inbound 940R transactions. This value shows in the existing TAC field. If the TAC is provided from the 940R, the field is closed for editing. If it is not provided from the 940R, the TAC is selected without requiring the Transportation Management Office Routing Identifying Code (TMO RIC). If a TMO RIC is selected, the TAC is mandatory.
The Originating Problem:
The Marine Corps (USMC) requires the Logistics Command (LOGCOM) Item Managers to be able to assign the TAC for use with the shipment of the Customer Requisition (CR), the Disposal Release Order (DRO), or the Redistribution Order (RDO). Currently DPAS has the TAC assignment within the Warehouse MRO process.
Impact:
TACs are now processed from incoming MROs into the Warehouse Materiel Release Order process and displayed on the Materiel Release Order record.
