Results for “hrfv_recruitment_activities”

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

Overview

The APPS.HRFV_RECRUITMENT_ACTIVITIES view is a business view template within the PER (Human Resources) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as the data source from which the flexfield view associated with recruitment activities is generated, exposing recruitment activity records in a denormalized, reporting-friendly format. The view is registered in the E-Business Suite Technical Reference Manual (ETRM) with a VALID status and is owned by the APPS schema.

The view consolidates recruitment activity header information — names, dates, costs, contacts, activity type, and coordinating organization — into a single queryable object. Because recruitment activities underpin sourcing, applicant tracking, and requisition management in Oracle iRecruitment and Oracle Recruiting, this view is frequently referenced by concurrent programs, Oracle Business Intelligence (OBIEE/BI Publisher) reports, and custom extensions that need to surface planned versus actual expenditures against recruitment campaigns.

A recurring search term associated with this object is planned_cost, reflecting the common need to report on budgeted recruitment spend. The view addresses this by exposing PLANNED_COST and ACTUAL_COST as numeric columns, both converted from their base storage format.

Underlying Base Objects

The view is defined over a combination of transactional tables and reference/security objects. Documented base objects include PER_RECRUITMENT_ACTIVITIES (SYNONYM), the primary transactional table holding recruitment activity records; PER_PEOPLE_F (VIEW), the effective-dated person view providing internal contact details; HR_ALL_ORGANIZATION_UNITS_TL (SYNONYM), joined twice to supply both the coordinating organization and the business group name; and HR_LOOKUPS for the recruitment activity type meaning (LOOKUP_TYPE = 'REC_TYPE').

Supporting packages referenced by the definition include HR_BIS (for the security profile business group filter), HR_SECURITY, HR_GENERAL, and HR_PERSON_NAME. IRC_ALL_RECRUITING_SITES_TL is listed among the referenced objects and is used in recruitment-related contexts.

Security is enforced through the predicate PRA.BUSINESS_GROUP_ID = NVL(HR_BIS.GET_SEC_PROFILE_BG_ID, PRA.BUSINESS_GROUP_ID), restricting results to the business group(s) permitted by the user's security profile. The view is defined WITH READ ONLY, preventing DML through the view layer.

Key Columns

• PLANNED_COST — The budgeted cost for the recruitment activity, cast via TO_NUMBER from the stored value. Central to budget-versus-actual reporting.
• ACTUAL_COST — The incurred cost to date for the activity.
• CURRENCY_CODE — Currency in which PLANNED_COST and ACTUAL_COST are denominated.
• RECRUITMENT_ACTIVITY_NAME — Descriptive name of the activity.
• REC_ACTIVITY_DATE_START / REC_ACTIVITY_DATE_END / REC_ACTIVITY_DATE_CLOSING — Start, end, and closing dates used for scheduling and aging analysis.
• RECRUITMENT_ACTIVITY_TYPE — Decoded meaning of the activity type from HR_LOOKUPS.
• INTERNAL_CONTACT_NAME / INT_CONTACT_EMPLOYEE_NUMBER — Internal owner of the activity.
• EXTERNAL_CONTACT_NAME / EXT_CONTACT_TELEPHONE_NUMBER — External contact details.
• COORDINATING_ORGANIZATION / COORDINATING_ORGANIZATION_ID — Organization running the activity.
• BUSINESS_GROUP_NAME / BUSINESS_GROUP_ID — Owning business group for security and partitioning.

Common Use Cases and Queries

Typical uses include recruitment budget tracking, activity pipeline reporting, and integration feeds into data warehouses. A representative query returning planned versus actual cost by activity is:

SELECT recruitment_activity_name,
       recruitment_activity_type,
       coordinating_organization,
       planned_cost,
       actual_cost,
       (planned_cost - actual_cost) budget_variance,
       currency_code
FROM   apps.hrfv_recruitment_activities
WHERE  rec_activity_date_start >= :p_start_date
ORDER  BY planned_cost DESC;

Filtering by coordinating organization or activity type supports departmental reporting, while the business group predicate ensures only authorized data is returned. Because PLANNED_COST and ACTUAL_COST are numeric, they can be aggregated directly for roll-up reports. Note that all joins to persons and lookups are outer joins, so activities without an assigned internal contact or type remain visible, preserving completeness in reporting.