Kontakt

Ansicht
Dokumentation

RPCPRSU0_CE - Payroll Reconciliation Report (Scheduler)

RPCPRSU0_CE - Payroll Reconciliation Report (Scheduler)

Vendor Master (General Section)   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

Title

Payroll Reconciliation Report (Scheduler)

Purpose

The Payroll Reconciliation Report (Scheduler) is used for the flow control of parallel and distributed reporting. Parallel and distributed reporting allows you to select persons, and to output report-specific data on selected persons in the SAP system. In the Payroll Reconciliation Report (Scheduler), the reconciliation report name (RPCPRRU0_CE) is defaulted, but you still need to specify a variant and other parameters for the report execution.

Distributed Reporting

Distributed reporting allows you to access data from systems that are run independently of your system. To do so, enter which report you want to run in the calling system. This report is then run in the called system via Remote Function Call (RFC). When the report has been run, the data is transferred back to the calling system, again via RFC. The data is then formatted, (sorted for example), and output in the calling system.

You can use distributed reporting to execute a central personnel check in a global enterprise that uses distributed data retention, for example. This would then allow you to execute reports for all employees in one single step.

Parallel Reporting

Parallel reporting allows you to process a report in a system using more than one session (and thus, more than one work process). When you process data, the system first determines the personnel numbers that are to be processed, and then distributes them equally among the individual work processes. The work processes then retrieve the data relating to the relevant personnel numbers. All resulting data is then output in a list.

If you use parallel reporting, you will notice that your system performance improves considerably.

Combination of Parallel and Distributed Reporting

You can also combine distributed and parallel reporting, by running distributed reporting via RFC in several systems, and parallel reporting in the called system. To do this, you must enter the RFC connections to the called system, as well as the number of sessions. In this way, you specify the systems in which parallel reporting is to be run, as well as how many sessions are required.

Integration

Prerequisites

The following prerequisites must be met in order for you to be able to run 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 than once
  • 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 (ensure that 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 any selections using organizational structures or search help selections

Features

Selection

Payroll Reconciliation Report (Scheduler) (RPCPRSU0_CE) can be run 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 specific version, ensure that you have enabled your custom report for distributed or parallel reporting.

with variant

Name of report variant to be run. To be able to run parallel or distributed reporting, you must enter a report variant.

Warning
You cannot use a report variant for parallel reporting if it contains a selection using organizational structures or a search help.

Number of sessions

Number of sessions (= work processes), among which parallel processing is divided. You can run a report parallel in the current system by entering an RFC connection. You can also use parallel processing by using distributed reporting. In this case, the specified number of sessions are opened in each system called.

RFC connections

RFC connections to systems in which the specified report variant is to be executed. You must use the multiple selection feature to enter all RFC connections for the systems to be called. Use NONE for parallel 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-out setting for background processing via following parameters:
    Main delay, Waiting time for next check and Number of repetitions.

Main delay

Determines how many seconds the lead system waits until it checks if the processes have been completed in the called systems. If all processes have been completed, the data is transferred from the called system to the calling system, and is subsequently output. If the processes have not yet been completed, further checks are performed independently of the waiting time and number of repetition entries.

Waiting time for next check

Determines how many seconds the calling system waits until it checks again, to see if all processes have been completed in the called systems.

Number of repetitions

Determines how often the calling system checks to see if all processes have been completed in the called systems.

Standard Variants

Output

The output fields correspond to the output fields provided by the report executed in a distributed manner. If the data is processed online, the output list is displayed directly on the screen. If the data is processed as a background job, an output job is created in the Job Overview. In order to view the generated spool file, choose menu option System->Own Spool Requests.

Note:

If you do not see a spool file after the background jobs are finished then you should verify the parameters:

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






Vendor Master (General Section)   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 8456 Date: 20240601 Time: 055848     sap01-206 ( 139 ms )