<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>+1<br>
Marc<br>
</p>
<br>
<div class="moz-cite-prefix">Am 09.05.2017 um 22:44 schrieb Nick
Clemens:<br>
</div>
<blockquote
cite="mid:CAA_eX3OEtn5F0=kiwuxvcATG85zf-+QzL_En29HxbvGrxYOCng@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>Hello All,<br>
<br>
</div>
With the current versions of Koha
there have been some changes in <span
class="inbox-inbox-lG">acquisitions</span>
and how prices are calculated and
there seems to be some confusion
in terms and how things are
currently being used.<br>
<br>
</div>
We wanted to clarify what is
happening, propose a change and get
feedback on what needs to happen.<br>
<br>
</div>
When placing an order there are
several price fields:<br>
</div>
Vendor price (listprice in db)<br>
-This is used to populate the
Replacement cost and budgeted cost on
the order page. It is not used against
the budget<br>
<br>
</div>
Replacement cost (rrp in db) <br>
-This is used to calculate the 'budgeted
cost/ecost' in the budget - it also
populates the replacement price in the
item created by the aqc process once
received<br>
<br>
</div>
Budgeted cost (ecost in db)<br>
</div>
-This is the replacement/rpp minus any
discount on the order - this is the value that
will be encumbered when the order is placed<br>
<br>
</div>
Actual cost (unitprice)<br>
</div>
-This is the eventual 'price' of the item and is
the encumbered amount once the item has been
received.<br>
<br>
</div>
With the changes that were made one can no longer
adjust the 'Replacement/RRP' once an order is placed
- this is because this value is adjusted for tax in
the db (rrp_tax_excluded, rrp_tax_included) and used
for calculating the ecost tax adjusted
(ecost_tax_excluded, ecost_tax_included)<br>
<br>
</div>
Some libraries have been having issues as they use
'Replacement' cost mostly for populating items and are
not used to it being unable to be edited and/or
affecting budgets.<br>
<br>
</div>
We are proposing to rename the current 'Replacement
cost' field to match the db value - 'Recommended retail
price' (RRP) and add a new 'Replacement cost' field,
editable at any point, that is only used for populating
the item field.<br>
<br>
</div>
We think this will clear up how the other values are being
used and restore functionality that changed.<br>
<br>
</div>
Please let us know if this works or what other suggestions
you have here.<br>
<br>
</div>
Thank you,<br>
</div>
Nick, Kyle, Jonathan</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Koha-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Koha-devel@lists.koha-community.org">Koha-devel@lists.koha-community.org</a>
<a class="moz-txt-link-freetext" href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a>
website : <a class="moz-txt-link-freetext" href="http://www.koha-community.org/">http://www.koha-community.org/</a>
git : <a class="moz-txt-link-freetext" href="http://git.koha-community.org/">http://git.koha-community.org/</a>
bugs : <a class="moz-txt-link-freetext" href="http://bugs.koha-community.org/">http://bugs.koha-community.org/</a></pre>
</blockquote>
<br>
</body>
</html>