310
In Dynamics GP 2010, when we attempt to close the year, we get the error message, "You must run the consolidate transactions and transfer detail to history utility to close the year." Someone suggested this must be caused by Analytical Accounting. Although we have AA installed, it is not setup let alone active. Any ideas what this message is asking us to do?
*This post is locked for comments
I am running into the same issue but I don't have the "move data to history" option. there is nothing for AA under Utilities. I do see one transaction in the AAG30000 table from 2015. it is a BBF transaction. AAG00104 has a company status of 1
Having empty AAG tables is something, and activating AA is another different thing. Status (4) means that AA is activated (the setup has been run before) on all the companies you mentioned.
Please check the AAG00102 table. The error you mentioned occurs; regardless of the table, when the next available value (aaRowID) indicated for (aaTableID) in the AAG00102 table has already been used.
Yes, I was able to close the year successfully and the sample of balances we looked at carried over. When doing the close, I did get another primary key violation error, but this time on the AAG40000 table. Incidentally, I copied the LIVE database over the test and reran the year end process and did not get the primary key violation on the AAG30000 table. Is it because it was created when I ran it the first time?
I just ran those scripts and the all three companies that we have setup have a company status of 4.
BTW....with the exception of third party products, MOST of the GP tables are created even if you do not install the app. For example, all of the payroll tables and all if the inventory tables exist even if you are ONLY using GL.
Run the scripts and see what happens.
And what happened next after moving data to history... Have you been able to complete the Year-End successfully?
Regarding the Activation of Analytical Account, please run the following scripts on DYNAMICS database, the second one retrieve the company id with a (4) status in case AA is activated.
- SELECT * FROM SY01500
- SELECT * FROM AAG00104
As for the primary key violation error, please refer to Knowledge base article 897280
Thanks Mahmoud.
My problem is that, although AA is installed, it is not setup, so I do not have any of those AAG3000X tables. I was able to run the Move Data to History but with each year it processed, I would get a Violation of Primary Key constraint 'PKAAG30000'. In SQL I verified that I did not have any table that starts with AAG3000X. However, it was able to let me run the transfer to history (or so it seemed) and it appeared to have closed the year successfully after all the years had been processed. i just don't know how successful that close was.
End-Year closing process includes a certain procedure that checks the historical years in Fiscal period versus the years in the AA open tables. The error; you mentioned above, occurs If there were data in the following Analytical Accounting tables ( AAG30000, AAG30001, AAG30002, AAG30003, AAG3000E ) for historical years
Therefore, moving data to history is a must. Go to Financial > Utility > Analytical Accounting > Move Data to History
You should include all historical years.
#1
André Arnaud de Cal...
292,516
Super User 2025 Season 1
#2
Martin Dráb
231,401
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
