We just ended our first official fiscal year in Tessitura. We had made sure that we had all new seasons and batch periods setup in system tables and all our new campaigns and production seasons were associated to the new fiscal year. However, it doesn't feel like Tessitura is recognizing that the 2015 fiscal year has ended for us. In the production element screens, it is still displaying productions/production season/performances associated to the just ended fiscal year, even if we select the current only box. And we have a stored procedure that assigns constituencies to patron accounts based on ticket history in the current season and it looks like the procedure is still looking at the previous fiscal year.
I double checked all our dates in system tables in regards to the batch period and season active dates and they all should have ended yesterday. Is there something more we need to do to get the fiscal year to rollover? Should I mark all the old periods and seasons as inactive in system tables?
First main thing is to check the "Inactive" column on the TR_SEASON table for those seasons. That should take care of much of what you indicate. Might also be worth double checking that you have taken all performances of that season off sale as well (that has gotten us a couple of times). If that are any hard set campaigns and appeals that need to be set to "Closed" as well, that could save you from some wrong source code issues.
Every organization has different setup, of course, but we create new campaigns and productions seasons for each fiscal year. Our fiscal years and our seasons don't quite align anyway, our fiscal year starts June 1st while our seasons actually overlap in terms of sales (pre-sales for the next season begin before the end of the current season).
Creating new campaigns/appeals/sources, etc. may sound like a drag, but it helps reporting immensely. In light of that we typically keep three fiscal years/seasons "active": generally speaking this is either the current season and two previous seasons or the current, previous and upcoming. This makes it easier to quickly bring up historical perspective in the client.
We actually have lots of concurrent seasons and campaigns: in light of that I've built a series of scripts to automate building out all our database items for each fiscal year (Campaign names, etc. are standardized).