Ansicht
Dokumentation

RPUCSRN0 - Changing of Savings Data in Payroll Past

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Purpose

Use this report to effect changes in savings data that has already been processed. This may be necessary in exceptional cases, such as if errors have been made that preclude the application of infotype Savings Schemes (0854).

Integration

Prerequisites

In order to start the report, you need the correct authorization. You must also be authorized to change savings data in infotype Savings Schemes (0854).

This report allows you to change data to the extent that it may no longer fulfill current or future (e.g. statutory) requirements. By using this report, you accept all associated responsibility and indemnify SAP of all accountability.

After correcting the savings data, a recalculation will begin in the payroll and all corrections will be processed. However, amounts already transferred (saved in the BT table) are not changed. An adjustment wage type will be made available to correct the difference between the transferred amount and the new savings amount. This claim from, or debt to, the bank/insurance company needs to be settled manually. No automatic correction will take place for amounts already transferred.

An additional call of the payroll function Savings Scheme Calculations (NLSPR) with 4th parameter 'CORR' is necessary in order to generate the adjustment wage types in the payroll. More information can be found in the documentation on this function.

To be able to use this report, it must be possible to update the infotype in the payroll history, which requires the field Response to Input in Payroll History (T582A-EPAST) to be set to value X using the IMG. It should be noted here that this change allows changes to be made in the history using transaction PA30. These changes will NOT effect any corrections in the payroll. When updating, this will appear in a message. The default setting for this field is E, so as not to allow any changes in the history.

Features

Selection

When making the selection, you can indicate to which person or persons the change should be carried out in the savings data that has already been processed.

Standard Variants

Output

Relevant savings data for all selected persons will be displayed in an ALV list. Double-click on a person to launch a pop-up screen where you can either choose to update the existing data in the current period, or to copy the data and change it in a different period. It is not possible to adjust the savings type (the savings or life-course subtype) directly.

Afterwards, the relevant data can be changed. Please take not of the following:

1. Add; adding new records is not possible using this report. Only existing reports can be changed.
2. Change; existing data can be adjusted, such as start and end dates, amounts, percentages, intervals, etc. It is not possible to alter bank details.
3. Delete; it is not possible to delete records. Saved amounts can be undone by setting savings amounts (and/or percentages) to zero.
4. Copy; use this operation to copy data to another period and change it.

If it is still necessary to switch between salary savings and life course schemes (or vice versa), first the savings amount must be set to zero. After that, call transaction PA30 normally to create a life-course savings record. As this is not possible retroactively, the period will then need to be adjusted using this report.

As soon as a change is made using this report, the next payroll period will be entered into the field Change Period for Retroactive Adjustments (SRPER) in infotype Savings Schemes (0854). This is the period in which the adjustment will take place. If the infotype record is copied, or a new record created, this period will not be transferred.

Activities

Example

rdisp/max_wprun_time - Maximum work process run time   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 4550 Date: 20240520 Time: 130946     sap01-206 ( 91 ms )