Updated Vacancies Are Not Being Self Approved And Result In Pending Approv
(Doc ID 284411.1)
Last updated on APRIL 04, 2025
Applies to:
Oracle iRecruitment - Version 11.5.9 to 11.5.10.2 [Release 11.5 to 11.5.10]Information in this document applies to any platform.
Symptoms
For vacancies which are being updated, and there is not any sort of approval process (using AME or anything else), Recruiters are the only ones allowed to update vacancies. You are noticing that these vacancies are sitting in the HR_WIP_TRANSACTION table as "PENDING_APPROVAL" and the HR_WIP_LOCKS table. You are also seeing (through the Workflow Admin responsibility), that most of these
are actually complete, but some of these are vacancies are "stuck" in the "Block" (WF_STANDARD.BLOCK). When this happens, the recruiters cannot go back into the vacancies to do any other updates. They get the following error: "You can not edit vacancy XYX changes to the vacancy
because (person name) has already submitted changes to the vacancy for approval"
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |