Search Results irc_vacancy_considerations_pk

Overview

HR.IRC_VACANCY_CONSIDERATIONS is a transactional table in the Oracle E-Business Suite HR (Human Resources) schema that stores the list of candidates being considered by a manager or recruiter for a specific vacancy. In the context of Oracle EBS 12.1.1 and 12.2.2, this object forms part of the iRecruitment data model, which manages requisitions, vacancies, applicants, and the pipeline of individuals under active consideration. The table holds one row per party considered against a given vacancy, together with a status flag indicating the disposition of that consideration.

From a Data Vault modeling perspective, the mined foreign key structure suggests this object behaves as a link entity. Its defining characteristic is the association between a vacancy and a party or person, rather than a standalone descriptive entity. A link classification is offered as a modeling suggestion only, derived heuristically from the FK relationships to PER_ALL_VACANCIES and the presence of VACANCY_CONSIDERATION_ID as a surrogate key.

Key Information Stored

The table contains eleven documented columns. The most significant columns and their roles are:

• VACANCY_CONSIDERATION_ID — Surrogate primary key, enforced by unique index IRC_VACANCY_CONSIDERATIONS_PK. It uniquely identifies each consideration row.
• VACANCY_ID — Foreign key to PER_ALL_VACANCIES, identifying the vacancy against which the candidate is being considered. Indexed non-uniquely via IRC_VACANCY_CONSIDERATIONS_FK1.
• PERSON_ID — The candidate person identifier considered for the vacancy. Indexed non-uniquely via IRC_VACANCY_CONSIDERATIONS_N1.
• PARTY_ID — The party identifier associated with the consideration, aligning the record within the trading community / party model.
• CONSIDERATION_STATUS — A VARCHAR2(30) value indicating whether the party is being considered for the vacancy, capturing the current disposition of the candidate.
• OBJECT_VERSION_NUMBER — A system-generated version counter that increments by one on each update, supporting optimistic locking and change detection.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard WHO audit columns recording creation and last-modification metadata for each row.

No business-key uniqueness beyond the surrogate primary key is documented; IRC_VACANCY_CONSIDERATIONS_PK is the sole unique index.

Common Use Cases and Queries

Typical scenarios include identifying all candidates being considered for a vacancy, tracking the consideration status of specific persons across requisitions, and joining consideration records to vacancy and person data for recruitment reporting. A straightforward retrieval pattern mirrors the documented query text:

• List all considerations for a vacancy: SELECT PERSON_ID, CONSIDERATION_STATUS FROM HR.IRC_VACANCY_CONSIDERATIONS WHERE VACANCY_ID = :p_vacancy_id;
• Find vacancies for which a person is under consideration: SELECT VACANCY_ID FROM HR.IRC_VACANCY_CONSIDERATIONS WHERE PERSON_ID = :p_person_id;
• Report pipeline by status: SELECT CONSIDERATION_STATUS, COUNT(*) FROM HR.IRC_VACANCY_CONSIDERATIONS GROUP BY CONSIDERATION_STATUS;
• Join to vacancy details: SELECT c.PERSON_ID, v.VACANCY_NAME FROM HR.IRC_VACANCY_CONSIDERATIONS c JOIN PER_ALL_VACANCIES v ON c.VACANCY_ID = v.VACANCY_ID;

These patterns support recruiter dashboards, candidate pipeline analytics, and audit extracts. Because OBJECT_VERSION_NUMBER increments on update, it is useful for detecting changed consideration records in incremental integrations.

Related Objects

The principal related database objects are driven by the documented dependency and FK structure:

• PER_ALL_VACANCIES — The parent vacancy table, referenced through VACANCY_ID. This is the primary join target for vacancy-oriented reporting.
• IRC_VACANCY_CONSIDERATIONS_PK — Unique index on VACANCY_CONSIDERATION_ID, defining the row identity.
• IRC_VACANCY_CONSIDERATIONS_FK1 — Non-unique index supporting the VACANCY_ID foreign key.
• IRC_VACANCY_CONSIDERATIONS_N1 — Non-unique index on PERSON_ID, supporting candidate-centric lookups.
• IRC_VACANCY_CONSIDERATIONS_WHO — The WHO audit trigger referencing this table, maintaining standard audit columns.
• APPS.IRC_VACANCY_CONSIDERATIONS — The APPS synonym/alias layer typically used by application code and ad hoc queries.

The table stores in the APPS_TS_TX_DATA tablespace, with indexes in APPS_TS_TX_IDX. The FND design data reference is PER.IRC_VACANCY_CONSIDERATIONS.