GP MEX: What is the Impact of Changing Accumulators Definition from Calendar End Date to Payment Date?
(Doc ID 2109130.1)
Last updated on OCTOBER 17, 2019
Applies to:PeopleSoft Enterprise HCM Global Payroll Mexico - Version 9.1 to 9.2 [Release 9]
Information in this document applies to any platform.
What is the impact of changing the MTD, QTD and YTD accumulators for MEX from being based on calendar period end date to payment date so that any earning/deductions elements calculated during the payroll process get stored into accumulator instances based on payment date instead of calendar period end date.
Suppose that customer used weekly calendars starting on W01 from 29-DEC-2014 to 04-JAN-2015. And hence, the last weekly calendar for the year will be W53 from 28-DEC-2015 to 03-JAN-2016.
In this case, when it is run the week 53 calendar based on calendar period end date, the earning element SUELDO POR H is calculated and the value gets added to accumulator SUELDO POR H's 2016 instance starting 28-DEC-2015 and ending 03-JAN-2016.
Whereas the requirement is to store all earning/deduction calculations for a quarter or an year within those year date ranges. So anything for YTD2015 should not be stored in a accumulator with 2016 end date.
Customer changed the accumulator SUELDO POR H to be based on payment date instead of calendar period end date and ran the W53 calc process on 31-DEC-2015. As a result the earning element SUELDO POR H in W53 was calculated and stored in 2015 accumulator instance.
What is the impact of changing the accumulator definition for all affected accumulators for Mexico? As per the analysis there are approximately 248 accumulators which might need to be changed. Many of these are PS delivered/Maintained.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document