Closed amenity closed 1 year ago
Scheduled spike discussion for Diana and me on 4/19/2023.
Related to #9808.
Met with Diana and discussed 2 questions Ronnie wanted us to explore:
Can we allow inventory items to be manually JVed before being closed?
CLOSED
Ready
at this time (ready for finance to process)Complete
(inventory planners have completed the inventory requestClosed
(work order including inventory request has been closed)Closed
status because some items are large ticket and items and Finance would like to see the JV process happen more immediately after the item is pulled by inventory.Can we enable manual overrides of TK + FDU values for individual inventory item transactions on the same work order?
Closed
to show up on the JV REPORTAttendees: Christina, Diana, Ronnie, Ivonne, Dan, Erin, Brian, Crystal, Melissa, Cesar
CLOSED
rule and have Ronnie review the JV report to ensure there are no red flags. Since the meeting Monday, I spoke with Billy about the possibility of listing a task order and an FDU for each inventory transaction rather than listing a single task order and FDU for the overall work order. This would eliminate the need to create separate work orders when inventory items are used at a location or for a project, but the items are funded from different FDUs or go to different task orders.
We feel that having separate task order and FDU fields for each transaction rather than for the overall work order would be beneficial in some cases. However, doing so would make the FDU review process more difficult and would introduce potential sources for incorrect data entry that could result in charges to incorrect FDUs. We do not feel that the benefits of such a change would exceed the potential for problems. Therefore, we would like to discontinue consideration of listing a task order and an FDU for each inventory transaction rather than for the overall work order.
We do want to continue consideration for
- the ability to process a transaction on a JV even if the work order has not been closed, and
- a revision to address cases where one (or more) “needs to be issued” items on a work order allow that work order to bypass the FDU Review queue and be included on a JV.
INSERT SCREEN SHOT
@ChristinaTremel set up work session with Diana for late this week/early next
Scheduled work session on 5/22 with Diana.
Journal Voucher Status
, rename to JV Status
#f6fa6b
, when JV status is not blank
inventory_transactions
, the "Journal Voucher Status" Rules 6 and 7
AND CHRISTINA (TEST)
to two work orders:
WRK23-185870
- checked that before the update the JV Status was "Not Ready"WRK23-185625
- checked that before the update the JV Status was "Not Ready"This shows us that the updated conditional rule is working and capturing that work orders do not have to be "Closed" to be put into a JV Status = "Ready".
5/23/23
- 910 records to update, two already show on the report
Schedule time to revisit this with Ronnie - 30 minute meeting
Schedule another time to present to the rest of the group when changes have been made.
ON HOLD
- 1/0 - number
work_order_signals
- INVENTORY_ON_HOLD
- 1/0 - number
Needs AIMS entry
on work_order_signals
, zero records foundInventory Request Status
field - Needs AIMS entry
to On Hold
WRK23-185870 - checked that before the update the JV Status was "Not Ready" WRK23-185625 - checked that before the update the JV Status was "Not Ready"
The Inventory Request Status is working correctly as expected. The JV Status is not changing even though we updated the Validation Rule # 6 and # 7. Need to keep trying and testing this.
WRK23-185870
Modified proposed Rule # 7, by added a new rule:
inventory_transactions
, the "Journal Voucher Status" Rules 6 and 7
work_order_signals
- INVENTORY_ON_HOLD
- 1/0 - number
Needs AIMS entry
on work_order_signals
, zero records foundInventory Request Status
field - Needs AIMS entry
to On Hold
thought we already added this to some of the AMD pages
Journal Voucher Status
, rename to JV Status
#f6fa6b
, when JV status is not blank
Had already created https://github.com/cityofaustin/atd-data-tech/issues/12601 - will close this one since new issue will address the changes.
Dedicated time to explore