My Oracle Support Banner

Why is the User Hook HR_PERSON_ABSENCE_BK2.update_person_absence_b Not Getting Executed as Expected While Updating an Absence From Self-Service. (Doc ID 1997121.1)

Last updated on JUNE 01, 2020

Applies to:

Oracle Self-Service Human Resources - Version 12.1 HRMS RUP6 and later
Information in this document applies to any platform.


Why is the User Hook HR_PERSON_ABSENCE_BK2.update_person_absence_b is not getting executed as expected while updating an Absence from Self-Service?

Customer is updating an Absence record from Self-Service Responsibility:

The parameter "p_date_start" and "p_date_end" for the user hook HR_PERSON_ABSENCE_BK2.update_person_absence_b called by the API HR_PERSON_ABSENCE_API.UPDATE_PERSON_ABSENCE get initialized with "hr_api.g_date" instead of picking up the dates from the table PER_ABSENCE_ATTENDANCES.date_start and PER_ABSENCE_ATTENDANCES.date_end.

This happens when the API is called on approving the leave request and the data is committed to the database.  The issue does not happen when the API and user hook are called first time when clicking on 'Next' button from the Absence Management Update page.
In this stage the issue is seen


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.