*This post is locked for comments
*This post is locked for comments
Thanks for this reminder. We will take this into consideration. This change has to happen so let's see how it goes.
We went through this a few years ago. In our case we were changing from a 7/31 year end to 12/31 so we were going to use 1211 to end 12/31/11. If I remember right everything in GP worked fine but we ran into an issue in FRx when trying to use the BASE function in columns to compare years. BASE-1 from 1211 becomes 1210. Unless it actually looks at the dates of the years this could also be an in issue in Management Reporter. Now it might not matter since having a stub year causes problems when making comparisons anyway. We had to set the columns in FRx manually when making comparisons to those years.
Has to be 4 numeric characters. 9914?
Well, that foils that plan! I didn't try it on my end. I should have before I suggested that. That makes sense though. Maybe 3014? 2114? I'm sure someone out there has a batter suggestion than I do.
I think it will need to be 214B. It will not let me enter more than 4 characters.
Do you have a test server? Try 2014B. I'm pretty sure that would work but test it first. Run GL, RM, SOP, POP, PM, ect transactions with that year and see how it looks in the GL. Run some reports too. Just remember that your reporting would have to look at year "2014B". I wouldn't use any special characters as SQL doesn't like them much. No dashes or things like that. 2014 and 2014B would remain "open" years until you did year end closing on them.
Thanks,
John Olley
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,280 Super User 2024 Season 2
Martin Dráb 230,214 Most Valuable Professional
nmaenpaa 101,156