Hierarchy
⤷ PY-US (Application Component) USA
⤷ P10C (Package) HR customizing: USA
IMG Activity
ID | OHAUTX00376 | Define retrocalculation based on payroll tables BAL/UNB |
Transaction Code | S_L7D_24002917 | (empty) |
Created on | 20120316 | |
Customizing Attributes | OHAUTX00376 | Define retrocalculation based on payroll tables BAL/UNB |
Customizing Activity | OHAUTX00376 | Define retrocalculation based on payroll tables BAL/UNB |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | OHAUTX00376 |
Use
In this Customizing activity, you define how retroactive differences in taxable wage types shall be processed by the system. The system can process these differences in one the following ways:
- It retrocalculates all payroll periods with entries in payroll table UNB or in payroll table BAL for reversed payroll periods.
- It triggers the flow of the differences to the payroll in-period by reading the amounts stored in the UNB/ BAL payroll tables (without retrocalculating all payroll periods).
Both options produce the same results from a payroll calculation and from a taxation standpoint.
Requirements
Standard settings
The standard system forces retro calculation for the oldest entry in UNB or BAL table due to the design of the Tax When Paid (TWP) process. The goal of this behavior is to carry the difference from retroactive periods to the payroll in-period.
If you have an employee with UNB table in a payroll period, and you have retrocalculation for this period due to an employee master data change, payroll function USTAX will force retrocalculation for the oldest entry in the UNB table, even though there is no master data change for the corresponding payroll period. The same is applicable for a reversed payroll period with BAL table in its result. For more information, see the Example keyblock below.
Activities
In the standard system, the TWPRE configuration option is set to blank. If it is blank or set to ON, the system forces retrocalculation for the oldest entry in UNB or BAL table.
If you want your system to retain the standard settings, you do not need to perform any activities.
If you do NOT want the system to trigger the retrocalculation, but rather to trigger the flow of the differences to the payroll in-period by reading the values stored in the UNB/ BAL payroll tables, execute this Customizing activity and change the value of the TWPRE configuration option to OFF.
Example
Example with configuration option TWPRE set to ON
An employee was hired with a salary of USD 1,000. In payroll period 4, his or her salary was changed to USD 400. The employee's claims will only be automatically cleared in payroll period 8. Consider the payroll results below:
For-period In-period Existing TWP tables
1 4 XDFRT(*)
2 4 XDFRT(*)
3 4 XDFRT(*)
4 4 UNB (**)
5 5 UNB (**)
6 6 UNB (**)
7 7 UNB (**)
8 8 BAL (***)
Period 9 has no BAL or UNB table. In payroll period 9, the employee's salary is increased form USD 400 to USD 500, retroactively to period 7. In this scenario, the system will force a retrocalculation for period 1 because of the entries in the UNB table in period 7, even though there is no master data change related to period 1. After you run payroll for period 9, the results in the system are as follows:
For-period In-period Existing TWP tables
1 9 XDFRT(*)
2 9 XDFRT(*)
3 9 XDFRT(*)
4 9 UNB (**)/XDFRT(*)
5 9 UNB (**)/XDFRT(*)
6 9 UNB (**)/XDFRT(*)
7 9 UNB (**)/XDFRT(*)
8 9 BAL (***)/XDFRT(*)
9 9 BAL
Example with configuration option TWPRE set to OFF
Consider the same situation described above. In payroll period 9, the system will NOT force a retrocalculation for period 1, since it will carry differences according to the amounts stored in BAL and UNB tables. After you run payroll for period 9, the results in the system are as follows:
For period In period Existing TWP Tables
7 9 UNB (**)/XDFRT(*)
8 9 BAL (***)/XDFRT(*)
9 9 BAL
Table legend:
(*) Because of change in Basic Pay.
(**) UNB table with the oldest entry related to period 1, because of claim generated in period 1 is not cleared (wage type /5PY lower than 0).
(***) Because claim is cleared in this payroll period (/5PY is greater than 0).
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | I | Valid for countries specified |
Customizing Attributes | Country Key | Country Name |
---|---|---|
OHAUTX00376 | US | USA |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | OHAUTX00376 | 0 | HLA0009692 | Tax |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
VV_T5F99K2_US_TW | V - View | SM30 |
History
Last changed by/on | SAP | 20120316 |
SAP Release Created in |