Running the Tax Code Uplift Report at Start-of-Year The procedure below is an SAP-recommended approach to running the
Tax Code Uplift Report
(RPUTCUG0) as part of your
Start-of-Year
processing.
You must have already received and stored your P9 data set, either locally or on your application server.
From the selection screen for the
Tax Code Uplift Report
(RPUTCUG0):
Maintain your person selection period entry, if required.
Specify the personnel numbers and payroll areas for which you wish the tax codes to be updated in the
Selection
group box.
Set the following additional data indicators in the
Processing mode
group box:
Apply General Uplift Indicator
Process Unchanged Tax Codes Indicator
In the group box
P6
(T)/P9(T) data source
, enter the complete path and the name of the dataset on the application server (or on your local system) where the P9 tape has been stored.
Choose
Execute
.
The report produces an SAP List Viewer (ALV) output of all employees included in the batch input session, grouped according to the source of the tax code change. The
Tax Code Uplift Report
output is displayed according to the type of processing that has occurred.
This is detailed in the following table:
Processing Type |
Description |
|---|---|
A1 |
Employee(s) have received a new tax code according to P6/P9 based on NI number match |
A2 |
Employee(s) without NI number have received a new tax code according to P6/P9 based on works number match |
B1 |
Employee(s) have received a new tax code according to general uplift |
B2 |
Employee(s) have received a new tax code according to general uplift Tax Basis W1/M1 changed to cumulative |
B3 |
Employee(s) have received a new tax code according to general uplift Tax Basis W1/M1 remains unchanged |
B4 |
Employee(s) have received a new tax code 0T due to general uplift |
B5 |
Employee(s) have received a new tax code 0T due to general uplift Tax Basis W1/M1 changed to cumulative |
B6 |
Employee(s) have received a new tax code 0T due to general uplift Tax Basis W1/M1 remains unchanged |
C1 |
Employee(s) tax code remains unchanged and is copied to a new record |
C2 |
Employee(s) tax code remains unchanged and is copied to a new record Tax basis W1/M1 changed to cumulative |
N1 |
Employee(s) tax code remains unchanged. No new record is created |
R0 |
Employee(s) are inactive on XX.XX:XXXX. No new record is created |
R1 |
Employee(s) do not have a current tax infotype record |
R2 |
Employee(s) already had a tax infotype record starting after XX.XX:XXXX |
R3 |
Employee(s) already had a tax infotype record from P6/P9 starting between YY.YY.YYYY and XX.XX:XXXX. No general uplift |
R4 |
Employee(s) already had a tax infotype record from P6/P9 starting between YY.YY.YYYY and XX.XX:XXXX. Record not copied |
R5 |
Employee(s) already had a tax infotype record from general uplift starting between YY.YY.YYYY and XX.XX:XXXX. |
R6 |
Employee(s) already had a tax infotype record due to this general uplift |
R7 |
Employee(s) tax code is not copied to a new record This tax code is not valid on XX.XX:XXXX |
R8 |
Employee(s) have not received a new tax code according to general uplift The new tax code is not valid on XX.XX:XXXX |
Z1 |
Records on P6/P9 have no matching NI / Works number among the employees selected |
Key:
XX.XX:XXXX : Begin Date for Copied Records
YY.YY.YYYY : Effective Date of Form
By choosing
Batch input process.
, you can go from the initial ABAP list view directly to the processing of the batch input session. The
Records rejected
option displays all records rejected by the report and the reasons for the rejection.