Allow User to generate a preview of fiscal year rollover

Allow user to generate a rollover report that will tell the user what errors may occur if rolling over with current data

• In preparation for rollover the library will run a report to catch any errors that may occur so they can be dealt with before the rollover is officially executed.

• In preparation for rollover the library will run a report to catch any errors that may occur on account of the rollover settings that are being used, so they can be adjusted before the current fiscal year ends.

• Library will always test rollover to make sure there are no surprises. Rollover may be tested more than once.

• When rolling over the system should provide a copy of the closing years budgets (Current state at end of year). This is used  as a reference to help verify the results of the rollover

Can 2 or more users run rollover preview at the same time? What behavior is expected?

Async operation - once started, the preview rollover will be executed on back-end, and the result will be available in history

Rollover setting is to be stored as well together with the results in order to enable/simplify further analysis

1 year is the max period for storing

All the data are stored in DB, and CSV can be generated via UI (as it's currently used in Acquisition app)

The question about the scope form Mikita

One of the option is not to have the history on UI but just provide an ability to download the file for the most recent rollover preview

How does the user user the preview is done? - E.g., by email

Try 2 options and estimates them

Does one need to support rollover preview not only for finances, but also for transactions and orders?

Unpaid invoices - it's just a prerequisite for preview

In fact, it's required to test the logic of budget_encumbrances_rollover.sql

I have done some mapping of the columns with fields of Budget record (see https://github.com/folio-org/acq-models/blob/13072225f182e5d88a8811aabcfd55bb497e78aa/mod-finance/schemas/budget.json)

1. Mapped fields are marked with
2. Some of the fields, though mapped, are readonly in the schema; this means that the data in the fields is calculated in real time; they are marked with
3. Some of the fields remained unmapped