Bug 1822

Summary: Global parameter in acqui. to require yes/no verification if over amount
Product: Koha Reporter: Chris Cormack <chris>
Component: AcquisitionsAssignee: Chris Cormack <chris>
Status: RESOLVED DUPLICATE QA Contact: Bugs List <koha-bugs>
Severity: enhancement    
Priority: P3 CC: jonathan.druart
Version: Main   
Hardware: All   
OS: All   
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:

Description Chris Cormack 2010-05-21 00:34:59 UTC 


---- Reported by drdrulm@yahoo.com 2008-02-09 06:25:30 ----

This year we had some entries that went over reasonable amounts. In aqui/circ and anywhere else money is involved, a limit could be set as a global parameter, and if the staff enters over this amount (abs(amount)) then a yes/no dialog would appear to verify the amount. This would keep errors to a minimum. I am searching through the orders to find the ones that tossed out budget into the millions! I found most of them, but this would be a nice check. 

Also, in Acqui., since there are estimated costs (I believe) a warning could be shown if the actual cost exceeded the estimated cost by some percentage, another nice check.



--- Bug imported by chris@bigballofwax.co.nz 2010-05-21 00:34 UTC  ---

This bug was previously known as _bug_ 1822 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=1822

Actual time not defined. Setting to 0.0
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here: chris@bigballofwax.co.nz.
   Previous reporter was drdrulm@yahoo.com.
Comment 1 Katrin Fischer 2011-08-15 06:07:13 UTC 
There are fields for 'encumbrance' and 'expenditure' in funds on current master.
But I am not sure there are checks for this values in the code and what kind of value is to be entered in the fields - percentage or amount?

Perhaps someone can check and update this bug.
Comment 2 Jonathan Druart 2013-03-15 11:03:51 UTC 

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