Is it possible to simulate a fiscal year change for testing/UAT purposes? We are going to change our fiscal year end next year, and I’d like to run some tests to verify all the changes will have the expected impact on our system.
The issue we’re having is the capture process cannot be run past today. Any thoughts on how this might be accomplished? Maybe simulate using journal entries?
So, when you see Epicor use their Addison database in demos, it seems like all of the transactions are recent, i.e. not embarrassingly outdated. So they must have a utility that advances every date in the system by a year or something.
If only you could do that in reverse, to rewind dates 1-2 years and then you should have enough of an onramp to test.
For those who remember the Y2K era (cough), there were tools that we ran that would intercept system date calls and allow use to see how the software would act. These tools still exist, here’s a few:
@Doug.C i’ve done this before. here’s a generic answer for you.
To test in your sandbox at the end of this month, you can edit the fiscal calendar so that november is the last month of the fiscal year and december is the first period of next year. from there it’s just the normal year end stuff like transfer balances.
if you use assets, there will be some extra steps.
we have some formulas to calculate the fiscal period on reports and dashboards because we are not ending the year on December 31. look for some of that too.
what are your current fiscal year dates and future fiscal year dates?
I did a query based on the TranGLC table and pulled out the data to put in as journal entries. It mimicked what we needed for the GL testing for Year End / RE Rollups.
Now to get used to not knowing what financial period it is anymore…