Acq year end: Non-propagated funds are not marked inactive

Bug #1948816 reported by Tiffany Little
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Undecided
Unassigned

Bug Description

When doing a year end rollover, funds that are marked propagate=false, rollover=false are left untouched by the rollover process. They remain active.

I would like to see these funds marked inactive as part of the year end process.

Real life example: This fiscal year a library has a grant that they won't have next year, or they're planning to reconfigure the way that they've laid their funds out. So since they don't want to have those funds next year, they set them not to be propagated. However, they are closing out the fiscal year, so they don't want those past year non-propagated funds to still be showing in their available list of funds in POs/invoices.

So I guess the sum of the bug would be that during rollover all past-year funds should be marked inactive, whether they are propagated or not.

Tags: acq acq-funds
Revision history for this message
Christine Morgan (cmorgan-z) wrote :

I can certainly see the use case Tiffany is describing and not having to mark the non-propagated funds inactive in that use case would be helpful. There are, however, some situations were a library needs to continue to pay out of previous years funds after fiscal close. These funds are not propagated and they remain active until all monies have been spent from them. Instead of having non-propagated funds set to inactive automatically at fiscal close, perhaps an additional checkbox option in the fiscal close dialog that says something like "Set all non-propagated fund to inactive" or something like that, could be added and only selected when appropriate. This would still allow libraries to set non-propagated funds individually to remain active or not.

Changed in evergreen:
status: New → Confirmed
Revision history for this message
Tiffany Little (tslittle) wrote :

I like Christine's suggestion. +1 from me

Revision history for this message
Wanangwa Hartwell (whartwell) wrote :

I also agree with Christine's suggestion.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.