Payroll Processing and PRRATEHIST Table

unknown

I would like to know if there is a company out there that archive the PRRATEHIST table to improve payroll processing performance or any other History table. We have more than 50,000 employees, process a bi-weekly payroll in 3 days, and are trying to improve our payroll processing performance, especially the PR140 run time. According to the Payroll processing flow, Lawson uses the PRRATEHIST Table to find the employee's rate of pay when left blank on the time record. We have employees hired back in 1976 and this table is building up because it doesn't only include rate of pay changes but any change (i.e. FTE) related to this field .

Any suggestions?
Thanks!

unknown

NZYRYI - The comment you made specific to the amount of data you have in PRRATEHIST isn't the issue with run time for PR140. While it's true, Lawson does use PRRATEHIST in the determination of pay rate defaulting when left blank on the timerecord, this is only relevant for the moment when the timerecord is created (keyed into PR33/35/36) or interfaced via PR530. Once the timerecord is created, PR140 does nothing to change it and the amount of data in that table has zero bearing on the earnings and deductions calc program. So, if your goal is to improve PR140 runtime (most especially) focus on something relevant such as reducing the number of timerecords being processed by say, bringing in weekly consolidated timerecords rather than daily time if you're interfacing via a timekeeping system. That would improve your results significantly. Or, try breaking your company into a few different processing groups and test the efficiency of running multiple PR140s at once (you may need to jimmy with job queues in order to allow this to occur). In the end, there will be only a few options afforded through the application and attacking it from a system resources standpoint may ultimately be the best way. Good luck!