Details
-
Bug
-
Status: Closed (View Workflow)
-
P1
-
Resolution: Done
-
None
-
ACQ Sprint 130
-
3
-
Thunderjet
-
R3 2021 Bug Fix
-
Increase the allowable encumbrance limit until your expense class can be added. Then lower it again.
-
Cornell, MI State University/Library of Michigan
-
Incomplete/missing requirements
Description
Overview: Encumbrance limit not calculating correctly when expense classes are involved. Orders can be opened when the budget clearly doesn't have enough money and Expense classes cannot be added to the budget when the encumbrance limit has been reached (But the calculation is not correct)
Steps to Reproduce:
- Log into some FOLIO environment as User X
- Click finance app
- create a budget with $1000 allocated
- Transfer $900 into this budget from a different budget
- Create an order with fund distribution for $1000 with Fund distribution 100% to this Fund and open it
- NOW $1000 is now encumbered against budget
- Create invoice for this order and approve and pay it
- NOW $1000 expended against budget
- Create new order for $1 for the same fund and open it
- NOW $1 is encumbered against budget and $1000 expended
- Add expense class to budget
Expected Results: Expense class is added to budget successfully
Actual Results: Error thrown. Expense class not added
Part two: Split out to separate story MODFIN-225
Create third order for $1000 for that Fund and expense classOpen order
Expected Results: Order can not be opened because the encumbrance limit (100%) for the budget has been reached.
Actual Results: Order is opened. Budget has $2001 unavailable but total funding is only $2000
URL:
Interested parties:
TestRail: Results
Attachments
Issue Links
- blocks
-
MODFIN-226 MODFIN(mod-finance) R3 Bugfix release
-
- Closed
-
- defines
-
UXPROD-3310 Thunderjet - Lotus (R1 2022) Tech Debt, NFR
-
- Closed
-
- is cloned by
-
MODFIN-225 Encumbrance limit not restricting order workflow
-
- Closed
-