I am not certain whether anyone might have to use more than one fiscal year in the same database. As I work on my financial database, the one that sent me looking into APIs and Json, I see different equities that might have different fiscal years. Most of what I have pay dividends March, June, September, and December, which probably corresponds to their fiscal year, although maybe not. But several have different payment schedules. So if I wanted one file to deal with several different equities, there might be a need to change the fiscal year according to needs.
The idea of using a permanent database option had never occurred to me, as I could not see much use for it in my applications. However, the idea of using it to hold a value immediately struck me. In particular, that might be useful for storing API tokens. My exploration of these has led me to some other services, like one for postal codes and address verification. Besides the USPS interface, there is at least one other, and it claims to work with other country’s codes. If there were a good way to store tokens, anyone could use the code as long as they signed up for the proper service. Many of them offer free introductory tokens which are limited in things like the number of calls that can be made within a certain time period, but those would be sufficient for most people’s situations, and if they needed more, they could subscribe for more.