GPAUS: TAX FM DET TAX WKS Doesn't Work Correctly With Retro Mid Period Segmentation
(Doc ID 2336583.1)
Last updated on MAY 02, 2018
Applies to:PeopleSoft Enterprise HCM Global Payroll Australia - Version 9.1 to 9.2 [Release 9]
Information in this document applies to any platform.
TAX FM DET TAX WKS fails to generate a result for TAX VR WEEKS AC (TAX AC TAX WKS SEG) where retro mid period segmentation is encountered.
When an employee has retrospective mid period segmentation, the final result in TAX AC TAX WKS YTD is too low.
Let's say the employee works July and August, both full months.
We would expect to see 8.666 weeks in TAX AC TAX WKS YTD in the August calendar.
However, if the employee had retrospective segmentation in July, with 2 weeks in the first segment and 2 weeks in the second segment, the value in the accumulator would only show 6.333 weeks. 2.333 weeks would be missing.
Process on cycle pay run (no segmentation).
Confirm TAX AC TAX WKS YTD holds the correct value.
Assign a retrospective event that will generate period segmentation (eg department transfer).
Use a middle of the month date for the transfer (eg 15th).
Process the following on cycle pay run.
Pay results for the prior calendar should now show as reversed and segmented on recalculation.
The current month should not have segmentation.
The employee has worked the two full months, but the end result in TAX AC TAX WKS YTD will not show the right amount.
In the last PAY segment for the retrospective calendar, there will be no instance of TAX AC TAX WKS SEG.
The accumulator will only show correctly in the first retrospective PAY calendar.
The current period calendar will show 4.333 weeks in this accumulator.
Because TAX AC TAX WKS SEG is missing in this second PAY calendar, the YTD value does not update correctly.
STEPS TO REPLICATE:
The issue can be reproduced at will with the following steps:-TAX AC TAX WKS YTD holds incorrect value where retro mid period segmentation is encountered.
2.Run July on cycle is processed.
3.Employee has 4.333 weeks in TAX AC TAX WKS SEG.
4.Employee is retrospectively transferred (mid period) to a different DeptID.
5.The August on cycle is run.
6.The employee’s July results are reversed and then segmented as a result of the retrospective transfer.
7.TAX AC TAX WKS SEG resolves to a value of 2 in the first July (recalculated) segment.
8.There is no instance of TAX AC TAX WKS SEG in the second July (recalculated) segment.
9.4.333 weeks shows in the TAX AC TAX WKS SEG accumulator for August (current period). At this point, the employee has worked for 8.666 weeks.
10.The employee only has 6.333 weeks in the TAX AC TAX WKS YTD accumulator in August. We are missing 2.333 weeks.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!