I'm not as well versed in PR2.0 yet but a brief look at the table gives me the impression that PR_Employee and PR_EmployeeHistory is meant to operate similar to SO_SalesOrderHeader and SO_SalesOrderHistoryHeader or SY_User and SY_UserHistory.
So if that is the case, does importing into PR_Employee to fix the problem records not update PR_EmployeeHistory?
Disclaimer, i have not tested importing into PR_EmployeeHistory but you can attempt the following to allow the table to be selected to import into.
If you really, really, really, want to attempt to import into PR_EmployeeHistory, you can use File > Run > SYZCON > DD > ENTER.
Select or type in PR_EmployeeHistory then click the Custom Info button.
Uncheck the "Exclude From VI Import" checkbox, click the Accept button, then click the Update File button.
------------------------------
David Speck II
Tennessee Software Solutions
------------------------------
Original Message:
Sent: 01-09-2020 16:56
From: Jeff Schwenk
Subject: Payroll 2.20 Experience: Please post here so we know if it's "safe" to install
Sounds like a data dictionary hack is in store
@Alnoor Cassim, @David Speck II, @Jim Woodhead , others??
------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------
Original Message:
Sent: 01-09-2020 16:09
From: Bernie Lehman
Subject: Payroll 2.20 Experience: Please post here so we know if it's "safe" to install
Hi Sue-
I was able to find the Retirement Plan field in the PR_Employee file and we also determined that when the first payroll of 2020 is run the box gets checked if the employee has a pension deduction. That alleviates the need to manually re-check the box for 2020. However, the issue I have is the Pension Plan flag in PR_EmployeeHistory is wrong on some employees and that screws up Aatrix. I'm trying to import to the PR_EmployeeHistory file to correct the data for the 2019 records and it's not listed as an importable file in VI. I can export from the file so it'e easy to get the records that are incorrect but I can't fix them.
Several clients have just fixed the check box in Aatrix but some clients want it fixed. I'm still stumped....
------------------------------
Bernie Lehman
Lehman Wesley & Associates
Original Message:
Sent: 01-09-2020 11:40
From: Sue Bennett
Subject: Payroll 2.20 Experience: Please post here so we know if it's "safe" to install
Bernie – It's there. We've had to import into that field multiple times. The table is PR_Employee, and the file is Retirement Plan – which is almost all the way at the bottom of the listed files. (Hint: You cannot type an "R" and hope to fine it – that doesn't work.)
Sue Bennett | President
P. 503 620 3484 | F. 503 620 2765
12559 SW 69th Ave | Portland, OR 97223
sue@benpor.com www.benpor.com
Bennett/Porter Blogs | facebook | twitter
Original Message------
I just reviewed the data from the large client and they have 169 employees where this is happening. They can fix the check box in employee maintenance but the W-2 form is incorrect in Aatrix. There is bad data in the PR_EmployeeHistory being used by Aatrix and it's easy to get an export of employees in 2019 that had a Pension Plan Amount but the flag is set to N - but I can't import the corrections back to that file because it's not listed in VI - WTH???
------------------------------
Bernie Lehman
Lehman Wesley & Associates
------------------------------