This content has been marked as final. Show 1 reply
Hope this isn't too late to help...
We have the exact opposite situation here. Our consultants designed our OPPM capital planning software to use hard-coded years (FY13, FY14, etc.), which required ridiculous amounts of billable hours for re-doing all the forms, scorecards, etc. every year during our "annual transition" to the next fiscal request cycle. When upper management decided to use COGNOS for reporting (since native OPPM output is so poor), and wanted historical reporting to past year's data, it was decided to use generic naming, with different tables using the same structure but including a field to denote which budget year to which it refers. This is MUCH better all around, and although it is expensive this cycle to make the change, it will save us a small fortune over time from no longer needing to re-work all the forms, scorecards, dashboards, etc. every year. And the COGNOS reports can just look-up the reference year to compare between any two or more sets of data for trends, comparitive reports, etc.
So, my advice is: DON'T CHANGE WHAT YOU HAVE! Good luck.