Shoot so did I. I'm just waiting for my client to call me back to get me connected.
I ran into issues setting the 2019 year at a client site last week too. Their hours were populating correctly on the report so I think it's a whole different issue. I ended up having to replace data dictionaries.
How to replace the data dictionary files in Sage 100 ERP
<content>
How to replace the data dictionary files in Sage 100 ERP
</content>
| Backup Warning |
|
Use caution when working with the below product functionality. Always create a backup of your data before proceeding with advanced solutions. If necessary, seek the assistance of a qualified Sage business partner, network administrator, or Sage customer support analyst.
|
| Database Warning |
| These steps require knowledge of database engines and application databases (DBs) used by your Sage product (including Microsoft/Transact SQL, Pervasive SQL, or MySQL, etc.). Customer Support is not responsible for assisting with these steps and cannot be responsible for errors resulting from changes to the database engine or DBs. Before making changes, backup all system and application DBs required for a full restore. Contact an authorized business partner or DB administrator for assistance. |
| Operating System Warning |
| This solution requires advanced knowledge of your computer's operating system. Contact your system administrator for assistance. Modifying your Windows Registry incorrectly can severely affect system operations. Sage is not responsible for operation issues caused by incorrectly modifying your Windows Registry. Always create a backup of your data before proceeding with advanced solutions. |
<content>
Some or all portions of the Data Dictionary files have become corrupted or unusable
</content>
<content>
Warning: Data dictionary files are critical to data integrity. Due consideration should be made before deciding to proceed with any of the three methods outlined below. Before attempting any of them, make sure you have a full backup set safely aside.
Method One: Rename the data dictionary folder and files, and Copy the files/folder from a backup (made before the problem began occurring) and paste them into the program.
(Note: User-defined fields (UDFs) created or updated since the time of the backup will have to be updated again to the data dictionary files, or there may be errors with lookups, reports, etc.)
- Via Windows Explorer, go to the "..\MAS90" location where Sage 100 ERP is installed.
- Rename the following files and folder:
- ..\MAS90\Providex.* (all Providex.* files files directly under "..\MAS90")
- ..\MAS90\SOA\SY0DCT.soa
- ..\MAS90\DDicts\ (the entire folder)
- Access the backup, locate the files listed above and copy them
(Note: The files should all be from the same backup set)
- Place the backup copies into their respective locations in the current, live installation.
Method Two: Rename the data dictionary folder and files, and Copy the files/folder from a new installation of your version of Sage 100 ERP (including same Product Update, third party enhancements if any, etc.)
(Note: If there are user-defined fields (UDFs), they must be updated again to the data dictionary files, or there may be errors with lookups, reports, etc.)
- Via Windows Explorer, go to the "..\MAS90" location where Sage 100 ERP is installed.
- Rename the following files and folder:
-
- ..\MAS90\Providex.* (all Providex.* files files directly under "..\MAS90")
- ..\MAS90\SOA\SY0DCT.soa
- ..\MAS90\DDicts\ (the entire folder)
- Access the new installation of Sage 100 ERP, locate the files listed above and copy them
(Note: The new installation must be the same version of Sage 100 ERP, same Product Update, same individual program fixes or hot fixes (if any), and same third-party enhancements)
- Place the new copies into their respective locations in the current, live installation.
Method Three: Rename the data dictionary folder and files, and reinstall the Sage 100 ERP program into the same location (including same Product Update, third party enhancements if any, etc.)
(Note: If there are user-defined fields (UDFs), they must be updated again to the data dictionary files, or there may be errors with lookups, reports, etc.)
- Via Windows Explorer, go to the "..\MAS90" location where Sage 100 ERP is installed.
- Rename the following files and folder:
- ..\MAS90\Providex.* (all Providex.* files files directly under "..\MAS90")
- ..\MAS90\SOA\SY0DCT.soa
- ..\MAS90\DDicts\ (the entire folder)
- Re-install Sage 100 ERP to the same location, selecting the Repair option when prompted.
- The renamed files and folder should be replaced via the re-intall process.
</content>
The year is required message when trying to setup new year in ACA Employers Maintenance
<content>
Modifications will write to the Data Dictionaries. For this reason you should not get your files/folders from someone else's program.
</content>
------------------------------
Mary Jo Krueger
Senior Software Consultant
CLA (CliftonLarsonAllen LLP)
Appleton WI
920-996-1176
------------------------------
Original Message:
Sent: 01-02-2020 09:15
From: Beth Bowers
Subject: 0 Hours on ACA report
I had high hopes for this, but still nothing. And just trying to get the record in there as a PIA. Even after creating a new record with the key of 2019, I couldn't officially save it in ACA Employer Maintenance. So I filled it out in DFDM by comparing to prior years. But still no hours on the report. :-(
------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625
------------------------------
Original Message:
Sent: 01-01-2020 17:00
From: Colleen Tulledge
Subject: 0 Hours on ACA report
I experienced this at a client on Sage2019 PR 2.20. I went into ACA Employer Maintenance and reselected the ACA form to use. When I hit "Accept" it told me that the 2019 year did not exist (though entries had been made in the year). In DFDM I found a blank key instead "2019". When I manually plugged in the year and reran the large employee report the employee count was populated.
------------------------------
Colleen Tulledge
CT-Solutions, Inc