Microsoft Dynamics GP (Archived)

Posting to recently closed year

(0) Share

Report

Posted on by ElmerUXC

505

Hello,

I have a customer who recently executed the year end close for 2013. This customer has:

1. The 'Posting to history' box checked under the Allow area in the general ledger set up window.

2. This customer also has the last period, under financials series, unchecked in the Fiscal Periods Setup.

3. And finally, 2013 is the most recent year with the historical year checked.

When the customer attempts to enter a journal entry with a 12/31/2013 date, he is receiving the following message:

'You cannot post more than one year prior to the first day of the earliest open year.'

Am I missing a step or has anyone seen this issue in the past? The version is GP 2010 SP 2 (11.00.1799(SP2)).

Thank you for your time

*This post is locked for comments

I have the same question (0)

All responses (11)

Answers (0)

Richard Wheeler 75,850 Moderator on at

Like (0)

Report

Are all years prior to 2013 closed?

support.microsoft.com/.../851093

This link may be useful.

Was this reply helpful? Yes No
Suggested answer

Mahmoud Saadi 32,738 on at

Like (0)

Report

By design, Dynamics GP pops up this message when you post to a historical year prior to the most recent one, the steps that you have mentioned are precise with nothing to add up.

I do believe. as Mr. Richard implies above, you do need to check the years prior to 2013.

Your feedback is highly appreciated,

Was this reply helpful? Yes No
ElmerUXC 505 on at

Like (0)

Report

Thank you for your responses.

My customer confirmed that all previous years leading up to 2013 are closed and have the 'Historical year' box checked for each previously closed year in the fiscal periods form.

Is there a table or some other flag I should be reviewing?

Was this reply helpful? Yes No
Richard Wheeler 75,850 Moderator on at

Like (0)

Report

Try running this script in SSMS against your company database and attach the results. SELECT distinct a.YEAR1, a.PERIODID, a.PERIODDT, a.PERDENDT FROM SY40100 a JOIN SY40100 b ON a.PERIODID<>b.PERIODID AND a.PERIODDT b.PERIODDT order by YEAR1, PERIODID Hopefully it finds nothing.

Was this reply helpful? Yes No
Suggested answer

soma 24,410 on at

Like (0)

Report

GP allow us to post one historic year prior to the earliest opening year.

For example: If you have the earliest opening year 2014 with all the prior years to this opening years are closed, for this scenario GP allow us to post one historic year 2013 prior to the earliest opening year 2014.

What is your earliest opening year?

Additionally, run the below query in SQL again company database and attach the result.

select * from SY40101

Your reply is much appreciated.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hello everyone!

We have GP 10.0 (SP5) in our company. Our year end was August. However, in 2013 the policy was changed and the year-end changed to December.

At that time 2013 year was open with the start and end date as 01-Sep-12 to 31-Aug-13. Our finance department decided to close this year 2013 and created year 1213 for the period 01-Sep-13 to 31-Dec-13 (4 periods).

Now, they have closed both 2013 and 1213 years with 2014 is open. So, the most recent historical year is 1213. They want to post adjustment entries for 1213, but the system is showing error message "you cannot post to history unless an open year exist." Please anyone could help us out in resolving this issue. Please find below the result set for table SY40101 below:

Was this reply helpful? Yes No
Justin Thorp 2,265 on at

Like (0)

Report

I would recommend not having an out of sequence year. I know that the Revenue and Expense Deferrals module will have issues with it, and so does Fixed Assets (it's years must run between 1900 and 2199 if I remember correctly. Also, I'm not sure how other addons will be affected by this (FRx/Management Reporter, etc...). And as you see for yourself even the GL module is not coping in full with this out of sequence year.

My recommendation is to use the fiscal period modifier (part of the professional services tools library), and recreate the periods. You may find that you need to create the historical years with an X-1 value (where X is was the year label was previously).

Thanks,

Justin

Was this reply helpful? Yes No
L Vail 65,271 on at

Like (0)

Report

Well, this certainly solves the mystery. You need to use the PSTL to correct these fiscal years.

Kind regards,

Leslie

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks for the solution.

I got PSTL and after successful installation and registration, I followed steps mentioned in below article (in Jonathan reply) for using Fiscal period modifier:

https://community.dynamics.com/gp/f/32/t/90891.aspx

Please also refer my new table for SY40101

However, when I did reconciliation it didn't update GL30000 table with the new year 2113 (instead of 1213). Due to this reason the summary balances starts showing ZERO (for the period of 2113 year).

I then run below sql to update 1213 to 2113 in GL30000

update TWO..GL30000 set hstyear = 2113 WHERE hstyear = 1213

After that, I again run reconciliation for finance for the year 2113. To my surprise, all of the balances are showing correctly. Now, for open years 2114, 2115, 2116 and 2117, I run below query

UPDATE TWO..GL20000 SET OPENYEAR = 2114 WHERE OPENYEAR = 2014 -- for each open years

and then run reconciliation. This step has also corrected entries for all open years.

However, I am still reluctant to apply these steps in live company because I have updated table manually from sql. Appreciate, if you could advise me if the above steps are correct and I should proceed with apply them on live company OR should I have to further verify sub-modules for history and open years transactions. Also, is there any way I could skip running update sql statements.

Regards,

Waliullah

Was this reply helpful? Yes No
Tony Jose 5 on at

Like (0)

Report

Waiting for the reply.

Regards,

Waliullah

Was this reply helpful? Yes No