Bug 12459 - clicking spent on acq main page not showing everything
Summary: clicking spent on acq main page not showing everything
Status: RESOLVED DUPLICATE of bug 14172
Alias: None
Product: Koha
Classification: Unclassified
Component: Acquisitions (show other bugs)
Version: Main
Hardware: All All
: P5 - low major (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-20 13:37 UTC by Nicole C. Engard
Modified: 2015-05-15 10:06 UTC (History)
5 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 Nicole C. Engard 2014-06-20 13:37:41 UTC
On the default page of the Acquisitions module, in the table "All available funds for Brooklyn Law School Library library", the "Spent" column logically displays the total spend for each Fund.  However, we've found that when clicking on a linked total amount in the "Spent" column, payments whose Item Records have been deleted are no longer there. These payments still show up in the baskets and invoices. In other words, this table of total funds on the Acq main page is obviously driven by baskets and/or invoices, since the totals are accurate, so we're wondering why, when clicking on a total, the individual payments are obviously not driving by the baskets/invoices, but rather the item records, as it seems. This makes the table somewhat useless, other than viewing the grand totals for funds.
Comment 1 Paola Rossi 2014-09-12 13:23:36 UTC
Using master 3.17.00.023, when clicking on the linked total amount in the "Spent" column, payments are no longer there, even if the Item Records have not been deleted.
I see "No data available in table".
Below "Sub total", the Shipping costs are correctly listed for all the invoices.
Comment 2 Katrin Fischer 2015-05-15 10:06:12 UTC
Going to attach a patch on 14172 that should fix this as well.
Problem also appeared when there was no item to begin with (subscription orders).

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