Skip to main content

PeoplePlanner: Integration error when entering sickness across two months: This absence has been partially paid up to

PeoplePlanner: Integration error when entering sickness across two months: This absence has been partially paid up to

H
Written by Harry Ledger
Updated over 3 months ago

You may find that an unavailability due to sickness in Access PeoplePlanner causes an error (see below) when the sickness spans two pay periods. This is typically seen when closing an open ended sickness.

ProcessEventMessage - Error occurred in 'AccessSelect.HR.Logic.DataHub.AbsenceCreatedHandler': This absence has been partially paid up to 28-02-2021. To change the absence end date you will need to make this record a fully paid absence by amending the absence end date to 28-02-2021 and then create a new record for any remaining absence after that date. Please use the 'Previous' button above to make any changes to this entry The transaction ended in the trigger. The batch has been aborted.

This is caused by the sickness exceeding the Paid up to date in SelectPay.
​
You will will need to acknowledge the error, and then edit the absence in AccessPeoplePlanner by closing the Unavailability on the paid up to date. You can then add any remaining period of leave as a new unavailability record or edit the record again to reflect true dates if the sickness is to be closed off before the paid up to date.
​
For example, Joe Blogs phoned is sick on the 2nd of March but could not tell HR when he would be back. On the 28th of March, Payroll closed the pay period. Joe then returned on the 1st of April. You would need to close their unavailability record in Access People for the 28th and then create a new absence for the 9th - 1st.

Did this answer your question?