CAUTION: This post is NOT intended for SQL Administrators who are not familiar with GP Table Structures. The following script may have serious implication on certain GP environments, so please use it at your own risk. This method is also not supported by Microsoft for obvious reasons.
This message was quite annoying when I created a Test Company in GP10 and restored a Production DB for R&D and Testing purpose.
Analytical Accounting windows didn’t get opened and was throwing the following error message:
There were several articles which cautioned / warned off from restoring only Company DB, which I am quite aware of. Because restoring another Company’s DB on to a Test Company will not have any issues unless it has got some products, like AA, depending heavily and real-time on DYNAMICS DB.
After a bit of R&D here and there, this is what I did. There is a table called AAG00104 in DYNAMICS Database, which is Analytical Accounting Company Setup table. I wrote an UPDATE on this table for the newly created company record as below:
SET aaCompanyStatus = 4, aaRelease = 10
WHERE CMPANYID = [Test Company ID Integer value]
This obviously worked in my environment and released the Test Company for AA usage.
As I mentioned at the start of this post, be cautious and do not venture into this unless you are sure of the consequences.
I am also not quite sure whether we have any fix for this issue, as I could not get one from CustomerSource or PartnerSource. I may have overlooked. Please do write a comment if we already have a script for this issue.