Results for “irc_rec_team_members_pk”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The IRC_REC_TEAM_MEMBERS table is a standard Oracle E-Business Suite table owned by the HR schema and delivered under the PER (Human Resources) product family. Its documented purpose is to store the list of people who are working on a particular vacancy, effectively defining the recruitment or requisition team assembled for a job opening. In EBS 12.1.1 and 12.2.2 the object carries a VALID status in the ETRM registry, indicating it is a supported, actively used repository rather than a legacy artifact.

From a dimensional modeling perspective, the metadata classifies this object with a heuristic Data Vault classification of link. This suggestion reflects the table's role as an associative construct: it connects a vacancy to the persons and jobs that participate in the recruitment effort, rather than serving as a standalone descriptive hub or a change-tracking satellite. Each row therefore represents a relationship instance — one team member on one vacancy — and the table's grain is naturally expressed by the composite of vacancy, person, and assignment attributes.

Key Information Stored

The table is documented with 16 columns and a single unique index, IRC_REC_TEAM_MEMBERS_PK, defined on REC_TEAM_MEMBER_ID. This column is the surrogate primary key and the only documented business-key candidate; there is no separate natural unique constraint recorded.

• REC_TEAM_MEMBER_ID — surrogate primary key uniquely identifying each team-member row.
• VACANCY_ID — foreign key to PER_ALL_VACANCIES, tying the member to a specific vacancy.
• PERSON_ID — the person assigned to the recruitment team.
• PARTY_ID — the trading-party identifier associated with the member.
• JOB_ID — foreign key to PER_JOBS, indicating the job context of the assignment.
• START_DATE / END_DATE — the effective window during which the member is active on the vacancy team.
• UPDATE_ALLOWED / DELETE_ALLOWED — flags governing the member's privileges on the vacancy record.
• INTERVIEW_SECURITY — controls the member's access to interview-related information.
• OBJECT_VERSION_NUMBER — optimistic-locking column used by the EBS framework.
• Standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN).

Common Use Cases and Queries

The table is primarily consumed by recruitment reporting and by the iRecruitment vacancy workflow. Typical queries resolve the team roster for a vacancy or determine which vacancies a given person supports.

SELECT rtm.vacancy_id, rtm.person_id, rtm.start_date, rtm.end_date
FROM hr.irc_rec_team_members rtm
WHERE rtm.vacancy_id = :p_vacancy_id
AND SYSDATE BETWEEN rtm.start_date AND NVL(rtm.end_date, SYSDATE);

Reporting use cases include auditing recruitment-team composition, validating interview-panel security through INTERVIEW_SECURITY, and joining to PER_ALL_PEOPLE_F or PER_JOBS to produce named team listings. Administrators also query UPDATE_ALLOWED and DELETE_ALLOWED to troubleshoot permission issues on vacancy maintenance.

Related Objects

• PER_ALL_VACANCIES — joined on IRC_REC_TEAM_MEMBERS.VACANCY_ID = PER_ALL_VACANCIES.VACANCY_ID; the parent vacancy.
• PER_JOBS — joined on IRC_REC_TEAM_MEMBERS.JOB_ID = PER_JOBS.JOB_ID; supplies job definitions.
• PER_ALL_PEOPLE_F — resolves PERSON_ID to the team member's name and employee details.
• IRC_VACANCY_TEAM (and related iRecruitment team views) — present the team roster to the application layer.
• PER_ALL_VACANCY_REQS — links vacancies and their requisition data, complementing team membership.
• HR_API / iRecruitment public APIs — create and maintain recruitment-team assignments programmatically.

Overall, IRC_REC_TEAM_MEMBERS is a compact associative table whose value lies in linking vacancies, people, and jobs within the Oracle EBS recruitment data model.