The changes were not applied because ORA-20001: This person is not eligible for the element associated with this absence type (Doc ID 1491590.1)

Last updated on MARCH 19, 2024

Applies to:

Symptoms

PRODUCTION issue on 12.1.3 - R12.HR_PF.B.delta.5

Functional issue:

When the final approver tries to approve leave of absence request through the worklist, the following error occurs:

Steps to Reproduce:

1. xxx Employee Self-Service
2. Absence Management
3. Create an Absence request
4. Submit to approval
5. Manager logs into the system, and approves the leave request from the Home Page Workflow Worklist
6. Department Leave Clerk logs into the system, and clicks on the ‘Approve’ button from the Home Page Workflow Worklist
7. Immediately an error appears stating “"Error: The changes were not applied because ORA-20001: This person is not eligible for the element associated with this absence type

Workaround:
'Retry' the workflows in Workflow Administrator responsibility, and the transactions are then committed to the database

Technical issue identified by the customer:

Problem Summary:
The l_job_name variable is limited to 100 characters in package HR_UTIL_MISC_SS.getJobNameNew

Problem Description:
The l_job_name variable is limited to 100 characters in package HR_UTIL_MISC_SS.getJobNameNew.
Some of the job, grades, positions and organization names in the database exceeds this. This results in an error. There is no exception handling in the code, so the following error is received:

"The changes were not applied because ORA-20001: This person is not eligible for the element associated with this absence type"

This is also affecting Absence management, Performance Management and OLM workflows

In Performance Management, employees having long job name receive an unexpected error when they try to open the Task List.

Cause

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