How to delete a fiscal year that was incorrectly created

Well is that time of the year again...

Most of you are in the midst of closing 2012 and getting Microsoft Dynamics GP configured for fiscal year 2013. If you are in this process of closing 2012, make sure to check out the Year-End closing procedures series over at the Microsoft Dynamics GP Support and Services team blog:

Microsoft Dynamics GP Year-End Closing Blog Series 2012 Schedule!!

The past few days however, I have had to address a number of calls asking for a little help deleting fiscal years that have been setup incorrectly. The following screenshot illustrates one of such issues:

Fiscal Periods Setup window
For the most part, users enter the correct start and end dates for the period, but mistype the fiscal year, which can cause a lot of headaches since there's no Delete button to remediate the situation. In addition, if the year is changed to 2013, the system will not allow you to create a new fiscal year with the start and end dates of a previously setup fiscal year.

So with no Delete button, where do you go?

Well, you can always resort to a little T-SQL to fix the problem by running the following script against the company database:

-- Created by Mariano Gomez, MVP
-- This code is licensed under the Creative Commons 
-- Attribution-NonCommercial-ShareAlike 3.0 Unported License.
-- http://creativecommons.org/licenses/by-nc-sa/3.0/legalcode
--
DELETE FROM SY40100 WHERE YEAR1 = 2103;
DELETE FROM SY40101 WHERE YEAR1 = 2103;
DELETE FROM SY40102 WHERE YEAR1 = 2103;
DELETE FROM SY40103 WHERE YEAR1 = 2103;

NOTE: in the above example the fiscal periods were properly setup to reflect 2013 start and end dates, but the year was incorrectly entered as 2103 - fat fingered if you will.

As is customary, please run this and any script against your test environment first to determine if you achieved the expected results. Backup your production databases environment prior to executing.

Once you have executed the script, please proceed to recreate the fiscal year and fiscal periods.

Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

Comments

Mike Lupro said…
A further post would be interesting after someone has created an incorrect fiscal year (with the correct start/end dates as shown) but has also closed the current fiscal year into the incorrect fiscal year.
February 22, 2013 at 1:22 PM
Mike Lupro said…
In a later post it would be interesting to show how to handle an incorrect fiscal year after the user has closed the current fiscal year into the new/incorrect fiscal period.
February 22, 2013 at 1:23 PM
Post a Comment

Popular posts from this blog

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

Image
Hello all! It's been quite a while since I've actually written anything of remote interest to anyone who follows my blog, but at the same time, you will be pleased to know that I've been quite busy in the consulting front, with upgrades, server migrations, complex multi-instance postings involving 10's of thousands of transactions, wrapping up some Field Service Automation projects, and the list goes on and on. This time around I want to bring to the forefront, an issue I encountered updating  from Microsoft Dynamics GP 2013 SP2 to Microsoft Dynamics GP 2013 R2 plus the latest service pack. Background My client requested a server migration to a new environment where they wanted to deploy Dynamics GP 2013 R2 web client (plus the latest service pack) and upgrade their relational database management system to Microsoft SQL Server 2014. This is something I'm absolutely comfortable with (for the most part) given also that my client was sitting at Microsoft Dynamics
Read more

Cannot insert the value NULL into column 'CONTACT' error when clicking on Items List in Navigation Pane

Image
Moving on from my previous article on a similar subject - see Cannot insert the value NULL into column 'BASEUOFM' error when clicking on Items List in Navigation Pane , I recently came across this error,  Cannot insert the value NULL into column 'CONTACT' when clicking on the All Purchasing Transactions list under the Purchasing Navigation Pane option, after performing an upgrade from Microsoft Dynamics GP 9.0 to Microsoft Dynamics GP 2010 R2. All Purchasing Transactions list error - Purchasing Navigation List The name of the global temp table - in this case, tempdb.dbo.##2093338- varies in almost all cases, but the end result of the error is the same. The issue has been identified running Microsoft Dynamics GP 2010 RTM, SP1 or SP2. Upon further review, the issue is due to bad data in the Vendor ID (VENDORID) column in the Purchasing Receipt History table (POP30300). In summary, if you have a purchasing receipt with a blank vendor ID or a vendor ID that doe
Read more

How to uninstall Microsoft Dynamics GP 10.0 if you cannot uninstall it by using the "Add or Remove Programs" feature

INTRODUCTION This article describes how to uninstall an existing Microsoft Dynamics GP v10 system if you cannot uninstall it by using the Add or Remove Programs feature (or Programs and Features in Windows Vista) in Control Panel. It is recommended that you verify that you cannot uninstall by using Add or Remove Programs first. MORE INFORMATION First, verify that you cannot uninstall Microsoft Dynamics GP by using Add or Remove Programs (or Programs and Features) To verify that you cannot uninstall Microsoft Dynamics GP by using Add or Remove Programs (or Programs and Features in Windows Vista), follow these steps. For Windows XP or Windows Server 2003: 1. Click Start, click Run, type control appwiz.cpl in the Open box, and then press ENTER. 2. Click to select Microsoft Dynamics GP 10.0 product from the application list, and then click Remove. For Windows Vista: 1. Click Start, type Programs and Features in the Search box, and then press ENTER. 2. Click to select the product to be un
Read more