- Article Type: General
- Product: Aleph
- Product Version: 19.01 and up
Changing the List Price field in an order for the reason of updating the encumbrances it does work for some orders and not for others. In all cases the staff called up the order and updated the List Price field and then updated the order record. In some cases the according budget in the encumber node showed the new updated money. In others it did not update the encumbrance original amount. When it did not work, the order log shows an error message of "Failed to Update budget transaction after invoice price ws changed". When it did work the order log shows "Encumbrance for budget ... altered to ..."
The library staff did not realize that it did not work in all cases. When they ran their 2010 fiscal year change acq_06_b, some orders encumbered at the correct new amount and others encumbered at the old amount even though the order record had been updated.
The "Failed to update budget transaction..." situation occurs when their are insufficient funds in the budget year against which the original encumbrance was created. If this encumbrance is left unchanged because of this, then the following year's budget will show the original encumbrance value. The process that rolls the encumbrances into the new budget year doesn't look at the order. It looks at the previous year's encumbrance.
- Article last edited: 27-Oct-2016