Rollover fails when fund contains "Planned budget" created by user

Description

Overview:

Both test and common rollovers fail when fund contains "Planned budget" created by user
Preconditions:

1.A user with following permissions is logged in:
-Finance: Execute fiscal year rollover
-Finance: View fund and budget
-Finance: View ledger

2.The following fiscal years exist:
-Current "Fiscal year #1"
-The next "Fiscal year #2"

3.An active Ledger related to current "Fiscal year #1" exists

4.Active fund related to the ledger created in Preconditions item #3 exists and has:
4.1."Current budget" with $1000 money allocation
4.2."Planned budget" with $500 money allocation

5.Ongoing order in "Open" status with one POL related to current "Fiscal year #1" is created, "Re-encumber" option is enabled

6."Fund distribution" accordion in POL has following settings:
6.1."Fund #1" = active fund created in Preconditions item #4
6.2."Value" = $150 (not exceeding "Fund #1" allocation created in Preconditions item #4.1)

7.A user is on "Ledger" pane with search results for Ledger from item #3

Steps to Reproduce:

  1. Click on Ledger from preconditions

  2. Click Actions->Rollover on "Ledger name" pane

  3. Fill the following fields:

  • "Fiscal year" = the next "Fiscal year #2",
    "Enforce all budget encumbrance limits" checkbox is Active,
    "Enforce all budget expenditure limits" checkbox is Active,
    "Close all current budgets" checkbox is Active,
    "Rollover allocation" checkbox in "Rollover budgets" accordion is NOT Active,
    "Adjust allocation, %" field in "Rollover budgets" accordion is blank,
    "Rollover available" checkbox in "Rollover budgets" accordion is NOT Active,
    "Add available as" dropdown field is specified as Transfer,
    "Set allowances" checkbox in "Rollover budgets" accordion is NOT Active,
    "Allowed encumbrance, %" field in "Rollover budgets" accordion is blank,
    "Allowed expenditure, %" field in "Rollover budgets" accordion is blank,
    "Ongoing encumbrances" option in "Rollover encumbrances" accordion is Active,
    "Based on" dropdown in "Rollover encumbrances" accordion is specified with "Initial encumbrance" option,
    "Increase by, %" field in "Rollover encumbrances" accordion is blank,
    "Ongoing-subscription encumbrances" option in "Rollover encumbrances" accordion is NOT Active,
    "One-time encumbrances" option in "Rollover encumbrances" accordion is NOT Active

4. Click "Test rollover" button

5. Click "Confirm" button

6. In "Postman" app (or similar tool):
Send the following GET request to appropriate host environment:
host/finance/ledger-rollovers-budgets

7. In "Postman" app (or similar tool):

Values in response for the executed test rollover should be the following:

  •  

    • "budgetStatus": "Active",

    • "allowableEncumbrance": 100.0,

    • "allowableExpenditure": 100.0,

    • "allocated": 500.0,

    • "awaitingPayment": 0.0,

    • "available": 350.0,

    • "encumbered": 150.0,

    • "expenditures": 0.0,

    • "netTransfers": 0.0,

    • "unavailable": 150.0,

    • "overEncumbrance": 0.0,

    • "overExpended": 0.0

8. In ""Finance" app:
Click "Actions" button -> select "Rollover" option on "Ledger name" pane

9. Fill the following fields exactly as it was made in Step #3:

  • "Fiscal year" = the next "Fiscal year #2",
    "Enforce all budget encumbrance limits" checkbox is Active,
    "Enforce all budget expenditure limits" checkbox is Active,
    "Close all current budgets" checkbox is Active,
    "Rollover allocation" checkbox in "Rollover budgets" accordion is NOT Active,
    "Adjust allocation, %" field in "Rollover budgets" accordion is blank,
    "Rollover available" checkbox in "Rollover budgets" accordion is NOT Active,
    "Add available as" dropdown field is specified as Transfer,
    "Set allowances" checkbox in "Rollover budgets" accordion is NOT Active,
    "Allowed encumbrance, %" field in "Rollover budgets" accordion is blank,
    "Allowed expenditure, %" field in "Rollover budgets" accordion is blank,
    "Ongoing encumbrances" option in "Rollover encumbrances" accordion is Active,
    "Based on" dropdown in "Rollover encumbrances" accordion is specified with "Initial encumbrance" option,
    "Increase by, %" field in "Rollover encumbrances" accordion is blank,
    "Ongoing-subscription encumbrances" option in "Rollover encumbrances" accordion is NOT Active,
    "One-time encumbrances" option in "Rollover encumbrances" accordion is NOT Active

10. Click "Rollover" button

11. Click "Confirm" button

Expected Results:

Rollover executed successfully, "Planned budget" allocation created by user is saved after rollovers (test and common) 
Actual Results:

Common Rollover has completed with errors, Budget close Success, Order rollover Success, Financial rollover Error.

Test Rollover response does not contain any values:

  {
            "id": "655e9140-b296-5d7b-8df0-d87f7217f1d5",
            "_version": 2,
            "ledgerRolloverId": "6a8692a4-6c69-4782-af4e-c1da3ca33cf6",
            "name": "Test N1-FYA2023",
            "fundDetails": 

{                 "id": "bd99cdfa-8300-4de1-85c9-28406fe9bef9",                  "name": "Test N1",                  "code": "Test N1",                  "fundStatus": "Active",                  "externalAccountNo": "322",                  "acqUnitIds": [],                  "allocatedFromIds": [],                  "allocatedFromNames": [],                  "allocatedToIds": [],                  "allocatedToNames": []             }

,
            "budgetStatus": "Active",
            "allowableEncumbrance": 100.0,
            "allowableExpenditure": 100.0,
            "allocated": 0.0,
            "awaitingPayment": 0.0,
            "available": 0.0,
            "encumbered": 0.0,
            "expenditures": 0.0,
            "netTransfers": 0.0,
            "unavailable": 0.0,
            "overEncumbrance": 0.0,
            "overExpended": 0.0,
            "fundId": "bd99cdfa-8300-4de1-85c9-28406fe9bef9",
            "fiscalYearId": "cec13440-bffc-4dee-8b84-dfc51185716e",
            "acqUnitIds": [],
            "metadata": 

{                 "createdDate": "2022-10-04T10:41:29.836+00:00",                  "createdByUserId": "4efe08c2-b1bf-4947-a840-2ef67aa54bd3",                  "updatedDate": "2022-10-04T10:41:29.836+00:00",                  "updatedByUserId": "4efe08c2-b1bf-4947-a840-2ef67aa54bd3"             }

,
            "initialAllocation": 0.0,
            "allocationTo": 0.0,
            "allocationFrom": 0.0,
            "totalFunding": 0.0,
            "cashBalance": 0.0
        },

AC:

  • The bug was fixed

  • Karate test was implemented following by test case in the description

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

5

has to be done before

relates to

Checklist

hide

TestRail: Results

Activity

Show:

Dennis Bridges November 25, 2022 at 6:46 PM

Test successful in bugfest-nolana

NinaChistova November 21, 2022 at 12:28 PM

Tested on https://bugfest-nolana.int.aws.folio.org/

Works as expected

Oleksii Petrenko November 8, 2022 at 2:24 PM

Deployed to Nolana bf. Please proceed with verification

NinaChistova October 28, 2022 at 9:24 AM

 "Status (Budget)" field is specified as "Active" after common rollover in the downloaded .csv file as expected

Dennis Bridges October 27, 2022 at 10:07 PM

Test successful in folio-snapshot.

Done

Details

Assignee

Reporter

Tester Assignee

Priority

Story Points

Sprint

Development Team

Thunderjet

Fix versions

Release

Nolana (R3 2022) Bug Fix

RCA Group

Legitimate regression

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created October 4, 2022 at 11:20 AM
Updated November 25, 2022 at 6:46 PM
Resolved October 27, 2022 at 10:07 PM
TestRail: Cases
TestRail: Runs