You’re offline. This is a read only version of the page.
Customer Opened 2015 and entered the wrong first day/last day 1/1/16-12/31/16. She has entered transactions in 2015 already. I attempted to just change the first day/last day under the fiscal period setup but received an error message . “The date cannot be part of a different fiscal year” I then tried to reconcile 2015, this did not correct the issue. I also tried to update the SY40101 to show the correct first day/last day and received a duplicate key error. My next steps were to delete 2015 in SY40100, SY40101, SY40102 and SY40103 and recreate it in GP but she has transactions entered for 2015 and not sure if by deleting the system tables were 2015 is mentioned if it will have any effect on those transactions?
*This post is locked for comments
That was a real scare for me - I had not used the PSTL for Fiscal Periods for sometime and it was a bit of a concern at first until I worked out all the details.
Back up and backup the backup - always a good plan.
Sorry Bill you are right it removes all fiscal period but good thing is we can recreate them the way it was using PSTL.
Thanks Bill, this tool worked like a charm. Fiscal periods are now correct!
One of the most important things to remember - is do a backup.
While in my test database, and looking at this question I managed to 'delete' all my fiscal periods by clicking one of the buttons on the screen.
No backup of the TEST now I have to restore from LIVE to recover.
Lesson learned. Do a Backup even when you are playing around the system.
Hi Shelly,
Fiscal year modifer doesn't delete all years, it can be used to create new years or modify existing years. Historical year remain same, you might have to run reconcile financial to make sure all are correct after correcting the fiscal years. Please refer the following KB from Microsoft.
I didn't even know this tool existed! It looks like it deletes all your fiscal years that have already been setup, then you have rekey all the years in? What does it do with the historical years? Do those have to be reentered in the fiscal period setup window as well?
Shelly don't attack the tables to 'remove' that data it will cause nothing but issues for you.
You need to use the PSTL Fiscal Period modifier tool. This is really the only way to fix the problem.
Trust me, we tried it your way, and we ending up wasting way to many hours and it was still wrong.
The tools are the only way to go.
Please fix the year 2015 using PSTL. take a backup before doing this.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (