Hello,
There's been a few comments made on this forum, so I wanted to add some information based on what I've seen here:
>>First, you won't lose your data if you recreate the table in PSTL, as long as you use these steps:
1. In the PSTL window, the 'Toolkit' utility is what you'll want to use.
2. In the Toolkit Options window, choose the 'Recreate SQL Objects' option and click Next.
3. In the System Diagnostics window, select the 'Financial' series and then select a table such as GL10110.
4. Still on this window, select the 'Recreate Selected Table' and also the 'Recreate Data for Selected Table(s)' in order to recreate the table with data intact.
5. Click on the 'Perform Selected Maintenance' to proceed. It will show some warning and confirmation boxes you'll need to click through. Once the table is re-created, you'll get a message letting you know that. Click OK.
>>In the few upgrade cases where we've seen the PM00204 / PM1099PeriodDtl error show, the main cause is that for some reason, the PM00204 table doesn't get updated with the new TEN99FATCAFILEREQ column.
If you resolve the issue by manually re-creating the PM00204 table with this missing column, make sure you also re-create the views, triggers, stored procedure and all related objects for this table, if you don't run it through the actual upgrade, as these objects need to know that there is a new column in the table, otherwise you may see errors such as "Number of results columns doesn't match table definition".
>>One potential cause of tables not getting updated with new columns during an upgrade, whether it be PM00204 or others, is if there are records in the DU000030 table held in the DYNAMICS/system database from a prior upgrade. If there are records in the DU000030 table from a prior upgrade, it can cause Utilities to think tables have already been upgraded and it won't try to upgrade the tables and you won't get any type of error until later in the upgrade when it attempts to create the new views, stored procedures, etc., and throws an 'invalid column' error because it's expecting new columns in the tables, but they're not there.
The recommendation is to make sure the DU000030 table is empty before starting ANY upgrade of the GP databases, whether it be a major version upgrade or just a service pack or hotfix upgrade.
Hopefully this helps!! Thanks all!!