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

Do I have to use those "Z-" currency IDs in GP?

Image
I know this seems like a trivia question, but recently I have come across a number of clients who have been using Microsoft Dynamics GP for a number of years and have been told by their former partners that they *must* use the predefined currency IDs created after adding the sample company, with no real explanation to support these claims. Case in point, my new client in Saudi Arabia, has been struggling for years to understand why they were told to prefix all currency IDs with the "Z-". So they went ahead and setup "Z-SR" for the Saudi Real. If you are familiar with Microsoft Dynamics GP and the sample company, Fabrikam, you may have noticed by now that after adding the sample company (which is not a requirement by any means), you will get a number of predefined currencies such as Z-US$ (US Dollars), Z-UK (British Pounds), Z-C$ (Canadian Dollars), Z-AUD (Australian Dollars), and so forth, accompanied by a number of exchange rate tables. If you are not familiar wi...
Read more

Microsoft Dynamics GP Scrolling Windows and Line Sequence Numbers

Image
I thought I would write about something meaningless that no one really thinks about. However, I realized that this is a compelling topic since it makes for some interesting discussion around the ability to insert line items withinin most transaction scrolling windows. Let’s take some time to understand where Line Sequence Numbers come from. A Line Sequence Number is auto generated by Dynamics GP and uses a seed value of 16,384 as a basis for the first line. Each subsequent line in the scrolling window is incremented by this number, so line number 2 would have a Line Sequence Number value of 32,768, line number 3 would have Line Sequence Number Value of 49,152, and so on. Since most GP transaction entry scrolling windows allow inserting rows in between line items, the newly inserted Line Sequence Number value is calculated as an average between the previous and the next line item sequences, i.e., if you were to insert an item in between row 1 and row 2 in the scrolling window -- keep in...
Read more