Payroll Split Program

[Former Member]

We are currently trying to decide if we should modify the standard split programs for payroll processing (RPCS0000 and RPCSC000).  Our issue is that we have many employees in our payroll areas that are no longer active.  This causes the split program to not balance the jobs very effectively. 

For example, we have 80,000 employees in one of the payroll areas.  Of the 80,000 employees, there are 20,000 employees that should be processed.  However, the split program is splitting out all 80,000 employees and causing the last few jobs to take substantially longer than the other jobs.

To resolve the above scenario we are planing on modifying the abap code where the program selects the employees to limit the number of employees that get split. 

Has anyone else done this?  Are there other recommendations on how we could solve our issue?

Thanks,

Geoff

[ted_dinh · Accepted solution]

In the split program, it calculates number of ees to be processed based on payroll area (in form 'SELECT_PERNR' regardless of status, and stores these ees in 'SELPERNR' internal table. It uses this number to split the jobs.

What you could do is to create an enhancement point logic at the end of this routine to eliminate un-wanted pernrs (e.g. those that are already terminated). Note, as there may be terminated ees you still want to run payroll for (e.g. paying severance), you may need to check further on these ees to see if it needs to process through payroll by looking at 'Run payroll up to in IT0003 prior to eliminating them.