Bug 12652 - Acq: Wrong fund charged for orders created from staged marc records
Summary: Acq: Wrong fund charged for orders created from staged marc records
Status: RESOLVED DUPLICATE of bug 20014
Alias: None
Product: Koha
Classification: Unclassified
Component: Acquisitions (show other bugs)
Version: 3.16
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-24 15:40 UTC by Jesse Maseto
Modified: 2019-02-04 22:42 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Maseto 2014-07-24 15:40:37 UTC
We have two budget years (FY14 and FY15). FY14 is inactive, FY15 is active. Both budgets have the same fund names (i.e. FIC, NONFIC).

If I create a basket and add an item from an existing record choosing a particular fund, it charges the item against the FY15 fund.
If I create a basket and add an item from a staged file choosing a particular fund, it charges the item against the FY14 fund.

This is a bug. Maybe it is matching on the fund name instead of the fund number?

We are working around this bug by renaming the FY14 funds making the fund names different.
Comment 1 Katrin Fischer 2014-08-02 21:20:51 UTC
Hi Jesse, c
Comment 2 Katrin Fischer 2014-08-02 21:21:23 UTC
That was supposed to be: Hi Jesse, changing the bug title to be a bit more descriptive :)
Comment 3 Barton Chittenden 2018-07-25 20:04:58 UTC
I suspect that this is a special case of either

Bug 14850: Funds from inactive budgets appear in 'Funds' dropdown on acqui/invoice.pl

or

Bug 20014: When adding to basket from a staged file item budgets are selected my matching on code, not id
Comment 4 Katrin Fischer 2019-02-04 22:42:15 UTC
I agree with Barton, that this reads exactly like the fixed bug 20014. Marking duplicate - Jesse, plz reopen of you still see this issue!

*** This bug has been marked as a duplicate of bug 20014 ***