Search Results per_recruitment_activity_for




Overview
Explore in AI Chat

Overview

PER_RECRUITMENT_ACTIVITY_FOR is a Human Resources (PER) transactional table in the Oracle E-Business Suite 12.1.1 and 12.2.2 data model. It resides in the HR schema and serves as the association table that links individual vacancies to the recruitment activities through which they are publicized or processed. In functional terms, a single recruitment activity such as a job fair, open house, campus drive, or advertising campaign may be used to market multiple vacancies, and conversely a vacancy may be promoted through more than one activity. This table materializes that many-to-many relationship, allowing recruiters to track which vacancies are covered by which activities and to report on activity effectiveness and pipeline composition.

Because the table exists purely to associate two independent entities, the ETRM relationship metadata classifies it heuristically as a link table within a Data Vault modeling suggestion. It is not a hub, since it does not represent a core business concept such as a vacancy or an activity, nor a satellite, since it stores no descriptive history of its own beyond standard audit columns. The link interpretation is consistent with its primary key being a surrogate identifier and its three foreign keys pointing to the business group, the vacancy, and the recruitment activity.

Key Information Stored

Common Use Cases and Queries

The most frequent use is answering which vacancies belong to a given recruitment activity, and the reverse. A typical join resolves descriptive names by traversing the foreign keys:

  • List vacancies for an activity: SELECT v.vacancy_name FROM per_all_vacancies v, per_recruitment_activity_for f WHERE f.recruitment_activity_id = :activity_id AND f.vacancy_id = v.vacancy_id
  • List activities promoting a vacancy: SELECT a.recruitment_activity_id, a.name FROM per_recruitment_activities a, per_recruitment_activity_for f WHERE f.vacancy_id = :vacancy_id AND f.recruitment_activity_id = a.recruitment_activity_id
  • Count distinct vacancies per activity for pipeline reporting, grouped by recruitment_activity_id and filtered by business_group_id.
  • Audit reconciliation of concurrent program loads using request_id, program_id, and program_update_date.

Because the table carries no effective dating, queries reflect the current association set rather than historical promotion dates.

Related Objects

  • PER_ALL_VACANCIES — joined on VACANCY_ID; supplies vacancy definition and status.
  • PER_RECRUITMENT_ACTIVITIES — joined on RECRUITMENT_ACTIVITY_ID; supplies activity definition, dates, and status.
  • HR_ALL_ORGANIZATION_UNITS — joined on BUSINESS_GROUP_ID; supplies the owning business group.
  • PER_RECRUITMENT_ACTIVITY_F_PK — the unique index enforcing the primary key and supporting lookups by RECRUITMENT_ACTIVITY_FOR_ID.
  • PER_ALL_PEOPLE_F / PER_ASSIGNMENTS_F — commonly used downstream with vacancies to report applicant and recruiter assignment relationships.