+1

On 10.05.2017 07:45, Josef Moravec wrote:
Does make sense to me.

Josef

st 10. 5. 2017 v 5:16 odesílatel Marc Véron <ve...@veron.ch <mailto:ve...@veron.ch>> napsal:

    +1
    Marc


    Am 09.05.2017 um 22:44 schrieb Nick Clemens:
    Hello All,

    With the current versions of Koha there have been some changes in
    acquisitions and how prices are calculated and there seems to be
    some confusion in terms and how things are currently being used.

    We wanted to clarify what is happening, propose a change and get
    feedback on what needs to happen.

    When placing an order there are several price fields:
    Vendor price (listprice in db)
    -This is used to populate the Replacement cost and budgeted cost
    on the order page. It is not used against the budget

    Replacement cost (rrp in db)
    -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

    Budgeted cost (ecost in db)
    -This is the replacement/rpp minus any discount on the order -
    this is the value that will be encumbered when the order is placed

    Actual cost (unitprice)
    -This is the eventual 'price' of the item and is the encumbered
    amount once the item has been received.

    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)

    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.

    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.

    We think this will clear up how the other values are being used
    and restore functionality that changed.

    Please let us know if this works or what other suggestions you
    have here.

    Thank you,
    Nick, Kyle, Jonathan


    _______________________________________________
    Koha-devel mailing list
    Koha-devel@lists.koha-community.org
    <mailto:Koha-devel@lists.koha-community.org>
    http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
    website :http://www.koha-community.org/
    git :http://git.koha-community.org/
    bugs :http://bugs.koha-community.org/

    _______________________________________________
    Koha-devel mailing list
    Koha-devel@lists.koha-community.org
    <mailto:Koha-devel@lists.koha-community.org>
    http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
    website : http://www.koha-community.org/
    git : http://git.koha-community.org/
    bugs : http://bugs.koha-community.org/



_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to