Load MARC Order Records screen Fiscal Year field only accepts current year.

[Dale Rigney]

Tested on 3.10.

The new angular Load MARC Order Records screen only accepts the current year (2023) in the Fiscal Year field. This causes item import issues when the fund for the item is not a 2023 fund. If your library has a active funds from the previous year your Evergreen will give you an ACQ_IMPORT_ERROR (no funds with code xxxx at orgs [xxx] error message.

The legacy screens will allow you to choose this year as well as past years.

[Lindsay Stratton (lstratton)]

The Fiscal Year selector in the Load MARC Order Records appears to be a drop down selection list, but it does not link to any ACQ fund related fiscal year data, presumably drawing from the OU setting Fiscal Year field, which is (apparently) configured in the database?

This is a massive issue for libraries with non-calendar year fiscal years.

We have libraries that FYs ending in May and July, where the FY is will be out of sync with the current year default for half the year.

See also bugs https://bugs.launchpad.net/evergreen/+bug/1486213 and https://bugs.launchpad.net/evergreen/+bug/1962622, related to managing fiscal year configurations and non-calendar year FYs support.

[Tiffany Little (tslittle)]

I can confirm this finding. The Angular interface pulls from the table acq.fiscal_year, and the Dojo interface used the open-ils.acq.fund.org.years.retrieve API to just cull a list of years based on the funds accessible to the logged-in user.

Per a discussion on the ACQ-L listserv, there are some sites that may have no entries in acqfy and have been peacefully using the Dojo LMOR interface for years without them because there's no connection between acq.fund and acq.fiscal_year. I created a follow up bug for that: bug 2021996.

I also bumped the importance to High, because as Lindsay notes it's a big problem for FYE. If I could express a preference, I would prefer the solution to be the solution for bug 2021996 because I think that has longer longevity. There's also the option of solving it by fixing bug 1956510 (adding an admin interface for fiscal years).

[Jennifer Pringle (jpringle-u)]

Thanks for bumping the importance to high Tiffany.

We have several libraries that run April to March fiscals and our January to December libraries often don't actually run year end until the end of January so it sounds like this bug would cause problems for most of our libraries.

[Christine Morgan (cmorgan-z)]

All of our libraries run July to June fiscal years so this is an issue for us as well.

Thanks Tiffany.

[Tiffany Little (tslittle)]

I do think this should stay as High Importance, but for what it's worth the workaround is just to add entries to acq.fiscal_year in the database (either via your sysadmin or putting in a ticket to your vendor).

[Terran McCanna (tmccanna)]

This will be fixed in 3.12 with the patch for https://bugs.launchpad.net/evergreen/+bug/2021992

Since it is a new feature with upgrade script changes, the 3.12 Release Team opted to not backport it, but libraries on older versions may be able to apply the fix locally.