[Koha-bugs] [Bug 8854] invoice filters don't all work

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8854

--- Comment #14 from mathieu saby <mathieu.saby at univ-rennes2.fr> ---
(In reply to Jonathan Druart from comment #13)
> (In reply to Galen Charlton from comment #9)
> > Hmm, the patches for bug 5336, which is now pushed, do not add an
> > aqorders.branchcode column.  Maybe something else does?
> 
> Galen,
> Finally I decided to abandon this field (see bug 11001).
> I am not sure searching by branch for invoices is relevant since orders from
> different branches can exist for a same invoice.
> Moreover I don't know if filtering on the patron branchcode is the better
> choice: if the aqbasketgroups.billingplace is different, results could be a
> source of misunderstanding. Given that libraries have different work flow
> for acquisitions, results could be good for some and wrong for others.
> Maybe should we simply remove the search by library for invoices?
> 
> I'm adding Katrin and Mathieu to this discussion.

Hi
Not sure of what could be the best solution.

But I can tell you how we deal with that in Rennes 2 : 

But the only time whe had to search invoices in Koha, it was to compare the
number and amount of invoices of Koha with the financial tool of the University
(Sifac), to fix discrepancies (invoices received in one tool and not in the
other...)
Koha invoices display was not good for that, so I had to make a SQL report.
The result look like that
Poste budgetaire    Fournisseur    N° facture    Nom facture    Frais de port
(montant)    Frais de ports (poste)    Qté reçue    Cout reel    Prix public
TTC    Prix remisé TTC    Cout reel * Qté    Cout reel * Qté + Frais de ports

The first column "Poste budgétaire" is the name of the fund, which in my
library includes the name of the branch. For ex : "BMUS" for Library of MUSic.

But if the name of the fund had not included the name of the branch, I probably
would have added 2 columns with basketgroup.billingplace and
basketgroup.deliveryplace.
Because, as we use basketgroups are our main "grouping entity" for our
relations with our vendors (they receive no info at all about our Koha
baksets), the relevant information for us are basketgroup fields.
But in some libraries it could be baskets fields I presume.


By the way, the filling of basketgroup.{delivery/billing}place should be
syspref dependant. Filling it with the connection site of the librarian is not
good at all for us, and I suppose we are not an isolated case.

Mathieu

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.