I have a few questions with respect to performance of the Payroll program RPCALCK0...from a DBA perspective, do...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
a. Which tables are accessed/updated during a payroll run? I know the cluster tables pcl2 and pcl3 T528C, T528B are impacted.
b. Any ideas on how we can improve our processing in terms of reducing the elapsed time(see more data below).
c. Do we need to re-org specific tables on a regular basis which will improve performance?
We have been looking at why the jobs are starting to run longer. Our initial investigation points to the database. The database size has grown, and is now approximately 450 gig. Six months ago it was about 375 gig.
The last time eval job completed, the total length of processing time is approx. 10 hours. This same process last year was taking approx 6.5 hours.
Are you using RPCS0000? This program will allow you to run a parallel execution of the payroll process and significantly reduce the system time. Your assessment of why the jobs are running longer is most likely dead one. The tables you have already identified are the majority of the accesses but you can do a database trace if you want to get all of them (Transaction ST05).
Read the documentation on RPCS0000 and attempt to set up your jobs to use it. The parallel process should cut the time pretty close to the total for a single threaded job divided by the number of jobs you split it into.
Dig Deeper on SAP HR management
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.