Search Results irc_vacancy_considerations




Overview
Explore in AI Chat

Overview

IRC_VACANCY_CONSIDERATIONS is an Oracle E-Business Suite table owned by the HR schema and delivered under the PER (Human Resources) product family. It records the act of consideration performed by a Manager or a Recruiter against a candidate and the vacancy to which that candidate relates. In practical terms, the table sits within the iRecruitment data model and captures the association between a party or person and a specific vacancy, together with the status of that consideration. Because recruitment activity in EBS is driven by candidate-to-vacancy matching, this object supports workflows such as shortlisting, screening progression, and recruiter or manager review of applicants.

From a Data Vault modeling perspective, the metadata heuristically classifies this object as a link. This classification is a modeling suggestion rather than a native Oracle construct: the table primarily resolves relationships between parties, persons, and vacancies, and therefore behaves like a transaction or association entity in a dimensional or Data Vault design. The presence of a surrogate primary key alongside foreign-key references to vacancy records reinforces this associative character.

Key Information Stored

The table is documented in the ETRM 12.2.2 physical schema with eleven columns. The most significant are:

The primary key is a surrogate identifier; the metadata does not document a separate unique business-key index beyond IRC_VACANCY_CONSIDERATIONS_PK. The combination of VACANCY_ID, PARTY_ID, and PERSON_ID functions as the meaningful business association.

Common Use Cases and Queries

Typical usage centres on identifying which candidates are under consideration for which vacancies, and on tracking consideration status through recruitment pipelines. A representative query joins considerations to vacancies:

  • SELECT vc.vacancy_consideration_id, vc.vacancy_id, vc.person_id, vc.party_id, vc.consideration_status FROM hr.irc_vacancy_considerations vc WHERE vc.vacancy_id = :vacancy_id;
  • Recruitment reporting that counts considerations by status for a given vacancy or recruiter.
  • Pipeline analysis joining PERSON_ID to PER_PERSONS to obtain candidate names.
  • Data extraction into a Data Vault or warehouse model, where the table loads as a link between hub_vacancy, hub_person, and hub_party.

Because the table carries standard audit columns, incremental extracts can use LAST_UPDATE_DATE as a high-water mark.

Related Objects

The most significant related objects are:

  • PER_ALL_VACANCIES — referenced by VACANCY_ID through the documented foreign key; the parent vacancy definition.
  • PER_PERSONS — joined via PERSON_ID to resolve the candidate's person details.
  • HZ_PARTIES — joined via PARTY_ID to resolve the candidate's party record.
  • IRC_VACANCY_CONSIDERATIONS_PK — the primary key constraint enforcing uniqueness of VACANCY_CONSIDERATION_ID.
  • iRecruitment candidate and application entities in the IRC module, which consume consideration data to drive applicant progression and status displays.

Together these objects provide the recruitment context in which consideration records are created, updated, and reported.