Title
Payroll Reconciliation Report (Scheduler)

Purpose
The Payroll Reconciliation Report (Scheduler) is used for theflow control of parallel and distributed reporting. Parallel anddistributed reporting allows you to select persons, and to outputreport-specific data on selected persons in the SAP system. In thePayroll Reconciliation Report (Scheduler), the reconciliationreport name (RPCPRRU0_CE) is defaulted, but you still need to specify avariant and other parameters for the report execution.
Distributed Reporting
Distributed reporting allows you to access data from systems that arerun independently of your system. To do so, enter which report you wantto run in the calling system. This report is then run in the calledsystem via Remote Function Call (
RFC). When the report hasbeen run, the data is transferred back to the calling system, again viaRFC. The data is then formatted, (sorted for example), and output in thecalling system.
You can use distributed reporting to execute a central personnel checkin a global enterprise that uses distributed data retention, forexample. This would then allow you to execute reports for all employeesin one single step.
Parallel Reporting
Parallel reporting allows you to process a report in a system using morethan one session (and thus, more than one
work process). When youprocess data, the system first determines the personnel numbers that areto be processed, and then distributes them equally among the individualwork processes. The work processes then retrieve the data relating tothe relevant personnel numbers. All resulting data is then output in alist.
If you use parallel reporting, you will notice that your systemperformance improves considerably.
Combination of Parallel and Distributed Reporting
You can also combine distributed and parallel reporting, by runningdistributed reporting via RFC in several systems, and parallel reportingin the called system. To do this, you must enter the RFC connections tothe called system, as well as the number of sessions. In this way, youspecify the systems in which parallel reporting is to be run, as well ashow many sessions are required.

Prerequisites
The following prerequisites must be met in order for you to be able torun distributed or parallel reporting:

• The systems being used must have an identical Customizing status


• The personnel numbers to be processed in the systems must be unique, in
other words, you must ensure that no personnel number occurs more thanonce

• The RFC system connections must be maintained correctly

All systems to be called must be entered in the calling system
The called system must be entered in the systems to be called (ensurethat the same name is used)

• You must have defined a variant for the report that you want to execute
with distributed reporting
You can use any report variant for distributed reporting
The report variant used for parallel reporting must not contain anyselections using organizational structures or search help selections

Selection
Payroll Reconciliation Report (Scheduler) (RPCPRSU0_CE) can berun with the following parameters:
Report Name
Technical name of the SAP standard reconciliation program, RPCPRRU0_CE,or a custom specific version. If you are using a custom specificversion, ensure that you have enabled your custom report for distributedor parallel reporting.
with variant
Name of report variant to be run. To be able to run parallel ordistributed reporting, you must enter a report variant.
Warning
You cannot use a report variant for parallel reporting if it contains aselection using organizational structures or a search help.
Number of sessions
Number of sessions (= work processes), among which parallel processingis divided. You can run a report parallel in the current system byentering an RFC connection. You can also use parallel processing byusing distributed reporting. In this case, the specified number ofsessions are opened in each system called.
RFC connections
RFC connections to systems in which the specified report variant is tobe executed. You must use the multiple selection feature to enter allRFC connections for the systems to be called. Use NONE forparallel reporting.
RFC-RFC connection
An RFC connection between calling system and called system. Use NONE
for parallel reporting.
Online/Background
Controls how the report is processed.


• If you choose Online, the general time-out setting applies to the
processing.

• If you choose Background, the report is executed as a background
job in the called and calling systems. You must control the time-outsetting for background processing via following parameters:
Main delay, Waiting time for next check and Number ofrepetitions.
Main delay
Determines how many seconds the lead system waits until it checks if theprocesses have been completed in the called systems. If all processeshave been completed, the data is transferred from the called system tothe calling system, and is subsequently output. If the processes havenot yet been completed, further checks are performed independently ofthe waiting time and number of repetition entries.
Waiting time for next check
Determines how many seconds the calling system waits until it checksagain, to see if all processes have been completed in the calledsystems.
Number of repetitions
Determines how often the calling system checks to see if all processeshave been completed in the called systems.

Output
The output fields correspond to the output fields provided by the reportexecuted in a distributed manner. If the data is processed online, theoutput list is displayed directly on the screen. If the data isprocessed as a background job, an output job is created in the JobOverview. In order to view the generated spool file, choose menu optionSystem->Own Spool Requests.
Note:
If you do not see a spool file after the background jobs are finishedthen you should verify the parameters:


• Main Delay


• Waiting time for next check


• Number of repetitions.

Main Delay + ( Waiting time for next check * Number ofrepetitions ) >= Total Expected Process Time.