Results for “recruiter_id”

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

Overview

HRFV_VACANCIES is an APPS-owned business view template in the PER (Human Resources) product, delivered in Oracle EBS 12.1.1 and 12.2.2. Its documented purpose is to serve as the business view template from which the flexfield view is generated, meaning it provides a denormalized, user-facing projection of Oracle HRMS vacancy data that has been registered for descriptive flexfield (DFF) exposure. The literal '_DF:PER:PER_VACANCIES:VAC' embedded in the select list identifies the flexfield context associated with the PER_VACANCIES entity, confirming the view's role in the flexfield view generation framework. For reporting and integration purposes, the view is significant because it resolves numeric foreign keys into readable names — organization, job, position, grade, people group, location, recruiter, and requisition — allowing external tools, BI Publisher reports, and custom extracts to consume vacancy data without repeated joins to reference tables.

Underlying Base Objects

The view is defined over a mixture of base tables, synonyms, and one nested view. Documented referenced objects include PER_VACANCIES (VIEW), PER_REQUISITIONS, HR_ALL_ORGANIZATION_UNITS_TL, HR_LOCATIONS_ALL_TL, PAY_PEOPLE_GROUPS, PER_ALL_PEOPLE_F, PER_JOBS_TL, PER_GRADES_TL, and HR_ALL_POSITIONS_F_TL, together with the HR_BIS, HR_GENERAL, and HR_SECURITY packages. The joins are predominantly outer joins (the (+) operator appears on organization, people group, job, position, grade, location, recruiter, and language predicates), with requisition and vacancy acting as the driving records. The language predicates use USERENV('LANG') against the translated (_TL) tables so that descriptions are returned in the session language. Security is enforced through HR_SECURITY, and the status value is translated by HR_BIS.BIS_DECODE_LOOKUP, which resolves the VACANCY_STATUS lookup code stored on PER_VACANCIES into its display meaning.

Key Columns

• VACANCY_STATUS — the column most directly relevant to the user's query term. It is derived via HR_BIS.BIS_DECODE_LOOKUP('VACANCY_STATUS', VAC.STATUS), returning the decoded lookup meaning rather than the raw code.
• VACANCY_NAME / DESCRIPTION — identity and free-text detail of the vacancy.
• NUMBER_OF_OPENINGS, BUDGET_MEASUREMENT_TYPE, BUDGET_MEASUREMENT_VALUE — headcount and budget attributes.
• VACANCY_START_DATE / VACANCY_END_DATE — mapped from VAC.DATE_FROM and VAC.DATE_TO.
• ORGANIZATION_NAME, JOB_NAME, POSITION_NAME, GRADE_NAME, PEOPLE_GROUP, LOCATION_NAME — descriptive attributes resolved from their respective reference tables.
• REQUISITION_NAME, REQUISITION_START_DATE, REQUISITION_END_DATE — requisition context for the vacancy.
• RAISED_BY, RECRUITER_NAME — full names from PER_ALL_PEOPLE_F.
• Surrogate ID columns — BUSINESS_GROUP_ID, GRADE_ID, JOB_ID, LOCATION_ID, ORGANIZATION_ID (NVL to -1), PEOPLE_GROUP_ID, POSITION_ID, RAISER_ID, RECRUITER_ID, REQUISITION_ID, VACANCY_ID — retained for joining and filtering.

Common Use Cases and Queries

Typical usage includes vacancy status reporting, open-position analysis, recruiter workload reporting, and budget-versus-openings extracts. A representative query filters on the decoded status:

• SELECT vacancy_name, organization_name, job_name, vacancy_status, number_of_openings, vacancy_start_date, recruiter_name FROM apps.hrfv_vacancies WHERE vacancy_status = 'Open' ORDER BY organization_name, vacancy_name;
• SELECT requisition_name, COUNT(*) FROM apps.hrfv_vacancies WHERE vacancy_status <> 'Closed' GROUP BY requisition_name;
• SELECT recruiter_name, SUM(number_of_openings) FROM apps.hrfv_vacancies GROUP BY recruiter_name;

Because status is returned as a decoded value, filtering should match the lookup meaning rather than the underlying code. Report authors should also note the outer-join semantics: descriptive columns may be null where the corresponding foreign key is unpopulated, and ORGANIZATION_ID is coerced to -1 rather than null. As an APPS-owned flexfield view template, HRFV_VACANCIES should be treated as a read-only reporting interface; any client-side extension takes place through the associated descriptive flexfield, not by modifying the view definition.