Search Results irc_vacancy_consideration_pk

Overview

The IRC_VACANCY_CONSIDERATIONS table is a core data object within the Oracle E-Business Suite Human Resources (PER) module, specifically supporting the iRecruitment functionality in versions 12.1.1 and 12.2.2. It serves as a transactional junction table that records the formal consideration of a candidate from a talent pool for a specific job vacancy. This consideration is typically initiated by a hiring manager or a recruiter within the application. The table's existence is fundamental to tracking the candidate selection workflow, enabling users to manage and report on which candidates have been reviewed or shortlisted for which open positions, thereby forming a critical link between vacancies and candidate pools.

Key Information Stored

While the provided metadata does not list all columns, the primary and foreign keys define its essential structure. The central identifier is the VACANCY_CONSIDERATION_ID, a system-generated unique primary key for each consideration record. The most critical foreign key is VACANCY_ID, which links the consideration to a specific open position defined in the PER_ALL_VACANCIES table. Based on its described purpose, the table would also logically contain columns to identify the candidate being considered (likely a PERSON_ID or CANDIDATE_ID linking to PER_ALL_PEOPLE_F or a candidate table) and potentially the recruiter or manager who performed the consideration, along with timestamps and status indicators. These columns would store the core data points of who is being considered, for which job, and by whom.

Common Use Cases and Queries

This table is central to recruitment reporting and process audits. A primary use case is generating reports for recruiters or hiring managers showing all candidates currently under consideration for their vacancies. Another key scenario is analyzing recruitment funnel metrics, such as the number of candidates considered per vacancy. A common SQL pattern would join this table to vacancy and person details to create a candidate shortlist report.

• Sample Query (Conceptual): SELECT vac.VACANCY_NAME, per.FULL_NAME FROM IRC_VACANCY_CONSIDERATIONS cons JOIN PER_ALL_VACANCIES vac ON cons.VACANCY_ID = vac.VACANCY_ID JOIN PER_ALL_PEOPLE_F per ON cons.PERSON_ID = per.PERSON_ID WHERE vac.VACANCY_ID = :p_vacancy_id;
• Audit Trail: Tracking the history of which candidates were ever considered for a role, even if not ultimately interviewed or hired.
• Process Integration: The data in this table likely feeds subsequent recruitment steps, such as scheduling interviews or making offers, within the iRecruitment workflow.

Related Objects

The table's integrity and meaning are derived from its relationships with other HR entities. As documented, its primary relationship is with the PER_ALL_VACANCIES table via the VACANCY_ID foreign key. This ensures every consideration record is tied to a valid, existing job vacancy. The metadata indicates a duplicate foreign key constraint listing, which may be an artifact but confirms this critical link. While not explicitly listed in the provided excerpt, based on the table's purpose, it must also relate to candidate or person tables (e.g., PER_ALL_PEOPLE_F, IRC_CANDIDATES) to identify the individual under consideration. The table is referenced by its primary key constraint, IRC_VACANCY_CONSIDERATION_PK, and is a likely parent to other iRecruitment transactional tables that record outcomes of the consideration, such as interview scheduling or assessment results.