Every time I create a new fiscal year in Dynamics GP or show customers how to do it, I get a little frustrated that I have to manually rename all the periods. Some users may not care that instead of January GP displays Period 1, but I donāt think that is very user friendly. So, for more years than I sometimes care to admit, I have been manually changing all the period names on the Fiscal Period Setup window. Well, no more.
The SQL code below can be used to rename the fiscal periods for a calendar fiscal year. If you have something other than a calendar fiscal year, you can easily modify this to suit your needs. And if you have different fiscal periods each year, you can add a filter specifying the year to the WHERE clauses, although at that point, unless you are updating many companies, it might not be worth it.
update SY40100 set PERNAME = 'January' where PERNAME = 'Period 1' update SY40100 set PERNAME = 'February' where PERNAME = 'Period 2' update SY40100 set PERNAME = 'March' where PERNAME = 'Period 3' update SY40100 set PERNAME = 'April' where PERNAME = 'Period 4' update SY40100 set PERNAME = 'May' where PERNAME = 'Period 5' update SY40100 set PERNAME = 'June' where PERNAME = 'Period 6' update SY40100 set PERNAME = 'July' where PERNAME = 'Period 7' update SY40100 set PERNAME = 'August' where PERNAME = 'Period 8' update SY40100 set PERNAME = 'September' where PERNAME = 'Period 9' update SY40100 set PERNAME = 'October' where PERNAME = 'Period 10' update SY40100 set PERNAME = 'November' where PERNAME = 'Period 11' update SY40100 set PERNAME = 'December' where PERNAME = 'Period 12'
As with any code, please use this carefully. If youāre not sure, make backups and test somewhere other than your live company.
Filed under: Dynamics GP, GP 10.0, GP 2010, GP 8.0, GP 9.0, GP SQL scripts, System/Setup SQL code Tagged: Dynamics GP, SQL code

*This post is locked for comments