Order: Error message does not indicate what Fund does not have money

Description

Overview: A message "One or more Fund distributions on this order can not be encumbered, because there is not enough money in the budget" but does not identify the fund or funds in question. 

Steps to Reproduce:

  1. Log into some FOLIO environment as User X

  2. Navigate to Orders app

  3. Make sure Fund restriction are in place for the fund you will use

  4. Create Order with a value higher than that of your chosen budget

  5. Click open order

Expected Results: Error message displayed "One or more Fund distributions on this order can not be paid, because there is not enough money in (FUND code)." 

Approach
Improve error handling in the org.folio.service.finance.budget.BudgetRestrictionService#checkEncumbranceRestrictions

Actual Results: Error message displayed "One or more Fund distributions on this order can not be paid, because there is not enough money in the budget" but does not identify the fund or funds in question. 

Additional Information:
URL:
Interested parties:

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

Look through order lines and Fund manually to identify which fund is short. For larger orders this could be very time consuming.

Attachments

2

Checklist

hide

TestRail: Results

Activity

Show:

Dennis Bridges March 31, 2022 at 9:37 PM

test successful in bugfest-lotus

Oleksii Petrenko March 30, 2022 at 9:15 PM

Deployed to Lotus BF. Please proceed with verification

Dennis Bridges March 23, 2022 at 4:59 PM

test successful in folio-snapshot

Andrei Shumski March 22, 2022 at 9:08 AM

Tested on folio-snapshot 

Done

Details

Assignee

Reporter

Tester Assignee

Priority

Story Points

Sprint

Development Team

Thunderjet

Fix versions

Release

Lotus (R1 2022) Bug Fix

RCA Group

Incomplete/missing requirements

Affected Institution

!!!ALL!!!

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created March 8, 2022 at 2:28 PM
Updated March 31, 2022 at 9:37 PM
Resolved March 23, 2022 at 4:59 PM
TestRail: Cases
TestRail: Runs