Search Results pro_next




Overview
Explore in AI Chat

Overview

APPS.HRFV_SALARY_PRO is a Business Intelligence System (BIS) view owned by the APPS schema and registered in FND Design Data under the product short name PER as PER.HRFV_SALARY_PRO. Its status is VALID across Oracle EBS 12.1.1 and 12.2.2. The view presents salary information together with the date range over which each salary record is effective, drawing on the pay proposal and pay basis model in Oracle HRMS. Because it is a BIS view rather than a transactional table, it is intended for reporting, extract, and integration workloads where a denormalized, human-readable projection of salary data is required, including descriptive text for coded values such as approval status, pay basis, and multiple components.

Underlying Base Objects

The view is defined over a set of HRMS and payroll synonyms, views, and packages supplied by the PER and PAY products. The documented base objects are:

Because HR_SECURITY is referenced, the view honors HRMS security profiles, so a query returns only the salary records the logged-in responsibility is permitted to see. The EFFECTIVE_TO_DATE_NN column reflects the standard HRMS effective-dating convention of substituting a high sentinel date for open-ended records.

Key Columns

The view exposes both descriptive and coded representations of the same attributes. Key columns include:

The search term "multiple_components_code" maps directly to the MULTIPLE_COMPONENTS_CODE column, which carries the coded value of the multiple components flag; MULTIPLE_COMPONENTS carries its descriptive equivalent.

Common Use Cases and Queries

Typical uses include salary extract reporting, audit of effective-dated salary changes, and integration feeds that require a single flattened row per salary record. To isolate rows involving multiple salary components, filter on the coded column:

  • SELECT person_name, employee_number, salary_amount, currency, effective_from_date, multiple_components_code FROM apps.hrfv_salary_pro WHERE multiple_components_code IS NOT NULL;
  • SELECT employee_number, annual_salary, pay_basis_code, approved_code FROM apps.hrfv_salary_pro WHERE effective_from_date >= :p_from_date AND effective_to_date_nn >= :p_from_date;
  • SELECT assignment_id, salary_amount, multiple_components, pay_basis FROM apps.hrfv_salary_pro WHERE assignment_id = :p_assignment_id ORDER BY effective_from_date DESC;

Queries should always be executed from a responsibility whose security profile grants the required access, since HR_SECURITY filtering is applied within the view definition itself.