Search Results salary_bases




Overview
Explore in AI Chat

Overview

HRFV_SALARY_PRO is a business view template owned by the APPS schema within the PER (Human Resources) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The view is documented as a "business view template from which the flexfield view is generated," meaning it functions as a bridge between the underlying transactional salary proposal data and the descriptive flexfield display mechanism used in Oracle HRMS reporting and integration. Its status is VALID, and it exposes a denormalized, business-friendly projection of proposed salary records for employees across assignments, payrolls, and pay bases.

In practical terms, the view answers the recurring business question: "what salary has been proposed for each employee, under which payroll and pay basis, over what effective dates, and against which currency and annualization factors?" By resolving lookups into display values and computing annualized salary amounts, it allows report authors and integration developers to query salary proposals without writing the joins themselves.

Underlying Base Objects

The view is defined over a set of documented PER and PAY base objects and synonyms. Per the ETRM metadata for 12.2.2, the referenced base objects are:

The join therefore combines salary proposals with assignment, person, payroll, pay basis and time period context, while package calls handle value translation and row-level security.

Key Columns

Common Use Cases and Queries

Typical uses include salary review reporting, payroll cost analysis, and downstream integration extracts. Because HR_SECURITY is referenced, results are normally filtered by the caller's security profile when invoked through the standard HRMS security-enabled path.

To list active proposals with their multiple-component indicator:

  • SELECT person_name, employee_number, salary_amount, annual_salary, multiple_components FROM apps.hrfv_salary_pro WHERE employee_number = :emp;

To isolate proposals flagged for multiple components:

  • SELECT person_name, salary_amount, effective_from_date FROM apps.hrfv_salary_pro WHERE multiple_components = 'Yes' AND effective_from_date BETWEEN :start_date AND :end_date;

To annualize and aggregate by pay basis:

  • SELECT salary_bases, COUNT(*) proposal_count, SUM(annual_salary) total_annual_salary FROM apps.hrfv_salary_pro GROUP BY salary_bases ORDER BY total_annual_salary DESC;

Because MULTIPLE_COMPONENTS is derived from PER_PAY_PROPOSALS.MULTIPLE_COMPONENTS, integrators should use the _CODE column when loading raw values and the decoded column only for presentation.