Hi Satyajit,
The PA10600 is a Project Accounting table. When Project Accounting is installed, this table holds data for Purchase Orders that link them back to Project Accounting. Sales Order Processing does not link to Project Accounting like Purchasing. Most likely what is happening is that your new GP install has the Project Accounting Module installed on it, where your old database did not have it. So your restored database does not have Project Accounting tables loaded, but your new install is expecting that you would have them because its installed.
You would have a couple of options.
1. If you are not going to be using Project Accounting, then Uninstall the Project Accounting modules on this GP install. You can do this through Programs and Features on the workstation find the Microsoft Dynamics GP application on the list and choose Change or Modify and remove the Project Accounting module from the install.
2. If you are going to be using Project Accounting moving forward, you would have to reinitialize Project Accounting on this company to add all of the Project Accounting tables to it.
The following blog post would have instructions to do this.
community.dynamics.com/.../quot-problem-ascertaining-version-information-quot-error-when-installing-or-upgrading-microsoft-dynamics-gp
ALWAYS MAKE BACKUPS OF YOUR DYNAMICS AND COMPANY DATABASES BEFORE PROCEEDING.
To re-initialize a feature so that GP Utilities will install it at the current version that you're launching GP Utilities from, we would use these steps and scripts:
A. First, we would need to remove the feature from the system tables, using these script examples:
1. Delete DYNAMICS..DB_Upgrade where PRODID = 258
2. Delete DYNAMICS..DU000020 where PRODID = 258
3. Delete DYNAMICS..DU000030 where PRODID = 258
B. Next, along with removing the feature records from the three system tables, we would also need to remove that feature's sub-feature tables, which is what Dynamics GP Utilities also looks at to determine whether a feature has been installed or not, when it doesn't find the records in the system tables, but the feature is mentioned installed (existing in the Dynamics.set and DynUtils.set files).
Based on the chart in the blog above you would also need to drop the PA10702 table (if it exists in the company, it probably does not in your case)
drop table PA10702
You would then need to launch Microsoft Dynamics GP Utilities on your workstation where you have Project Accounting installed (i.e. present in the .set files) and this should add all of the Project Accounting tables to your company at the current version/build of the GP application.
***NOTE: When the re-initialization of a feature is performed, all SQL objects in the databases are dropped and re-created for that feature, which means the tables are also dropped and re-created, so when deciding whether or not to perform this process, you'll want to make sure that the feature was never used or there isn't any data for the feature that needs to be kept in Dynamics GP before moving forward with this process.
I hope this helps!
Isaac Olson
Microsoft Support
Share
Report
50
All responses (
Answers (
