Bug 26878

Summary: Add ability to prevent spending against parent funds
Product: Koha Reporter: Andrew Fuerste-Henry <andrewfh>
Component: AcquisitionsAssignee: Bugs List <koha-bugs>
Status: NEW --- QA Contact: Testopia <testopia>
Severity: enhancement    
Priority: P5 - low CC: barbara.johnson, bugzilla, nick, rkuiper
Version: Main   
Hardware: All   
OS: All   
See Also: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23767
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16126
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22329
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:

Description Andrew Fuerste-Henry 2020-10-30 17:48:05 UTC
Some libraries construct their funds such that parent funds aren't meant to be spent against directly. Instead, it is expected that the combined child funds will wholly account for the parent. It would be nice to somehow block spending against those parent funds and exclude them from fund selection dropdowns.

It'd be more flexible to set this in the fund with some sort of "do not spend against" flag.

On the other hand, it'd be simpler as a system preference that just says Do/Don't allow spending against parent funds. Or maybe the options could be "Do allow/ Don't allow / Allow only when child total = parent amount."
Comment 1 Katrin Fischer 2020-10-30 22:21:06 UTC
I like both ideas. We usually would want the parent funds not to be used for orders, but only the lowest "level" funds.
Comment 2 Andrew Fuerste-Henry 2021-02-03 16:34:50 UTC
Giving this a bump based on conversation in bug 23767 and bug 16126.

Currently, Koha supports two different conceptions of parent/child funds and that ambiguity necessitates complexity in the UI.
Comment 3 Katrin Fischer 2021-02-06 18:06:48 UTC
(In reply to Andrew Fuerste-Henry from comment #2)
> Giving this a bump based on conversation in bug 23767 and bug 16126.
> 
> Currently, Koha supports two different conceptions of parent/child funds and
> that ambiguity necessitates complexity in the UI.

+1
Comment 4 Barbara Johnson 2021-08-16 20:04:16 UTC
+1 Yes, let's do this.