Results for “percentage_increment”

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

Overview

HRFV_SALARIES is a business view template owned by the APPS schema in Oracle E-Business Suite, defined within the PER (Human Resources) product family. It is documented as valid in both ETRM 12.1.1 and 12.2.2. The view presents a consolidated, reporting-oriented projection of salary proposal and compensation data linked to employee assignments, grades, positions, payrolls, and performance reviews. Its name follows the "HRFV" naming convention used for flexfield business view templates—views generated by the flexfield view generation process. As such, HRFV_SALARIES serves both as a reporting surface for compensation analysis and as a template consumed when generating descriptive flexfield views that expose salary context to end-user inquiry screens, concurrent reports, and integrations.

Underlying Base Objects

The view is defined over a substantial set of PER and PAY base objects, joined through the APPS synonym layer. Documented referenced objects include PER_PAY_PROPOSALS (driving salary proposal rows), PER_ASSIGNMENTS_F, PER_PEOPLE_F, PER_PERIODS_OF_SERVICE, PER_ALL_POSITIONS, PER_EVENTS, PER_GRADES_TL, PER_JOBS_TL, PER_PERSON_TYPES, PER_PAY_BASES, and PER_PERFORMANCE_REVIEWS. Payroll and element context comes from PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_ENTRY_VALUES_F, PAY_ELEMENT_TYPES_F, PAY_INPUT_VALUES_F, and PAY_ALL_PAYROLLS_F. Organization and location descriptors are drawn from HR_ALL_ORGANIZATION_UNITS_TL, HR_ORGANIZATION_INFORMATION, HR_LOCATIONS_ALL_TL, and HR_ALL_POSITIONS_F_TL. Business logic is supplied by the PL/SQL packages HR_BIS (lookup decoding), HR_GENERAL, HR_PERSON_NAME, HR_SECURITY, and PER_VIEWS_PKG (grade comparatio calculation).

Key Columns

• BUSINESS_GROUP_NAME, PERSON_NAME, EMPLOYEE_NUMBER, ASSIGNMENT_NUMBER — identity and organizational context for the employee.
• SALARY_AMOUNT (PROPOSED_SALARY_N) and ANNUAL_SALARY — the proposed salary and its annualized equivalent, derived using PPB.PAY_ANNUALIZATION_FACTOR.
• PAY_BASIS — decoded through HR_BIS.BIS_DECODE_LOOKUP('PAY_BASIS', PPB.PAY_BASIS); this is the column most commonly searched, exposing whether pay is expressed on an hourly, daily, monthly, or annual basis.
• PREV_PAY_BASIS — currently returns NULL, reserved for prior pay-basis comparison.
• SALARY_CHANGE_DATE, SALARY_CHANGE_REASON, APPROVED_FLAG — proposal timing, decoded reason, and whether an element entry confirms approval.
• ABSOLUTE_INCREMENT, PERCENTAGE_INCREMENT — placeholders returned as NULL by TO_NUMBER(NULL).
• GRADE_COMPARATIO — computed by PER_VIEWS_PKG.PER_CALC_COMPARATIO using assignment, grade, rate, and working-hours inputs.
• GRADE_RATE_BASIS, CURRENCY_CODE, SALARY_AMOUNT_UNIT_OF_MEASURE — rate and currency context.
• WORKING_HOURS_AMOUNT, WORKING_HOURS_FREQUENCY, POSITION_WORKING_HOURS, NUMBER_PER_FISCAL_YEAR — working-time normalization inputs.
• PERFORMANCE_REVIEW_DATE, PERFORMANCE_RATING, RANKING, HIRE_DATE — performance and service context.

Common Use Cases and Queries

Typical applications include compensation review reporting, salary-increase analysis, grade comparatio monitoring, and integration feeds to downstream HR or budgeting systems. Because PAY_BASIS is decoded to a meaningful label, the view is convenient for filtering by pay basis without joining PER_PAY_BASES directly.

Example query listing recent salary proposals by pay basis:

• SELECT person_name, employee_number, salary_amount, annual_salary, pay_basis, salary_change_date, salary_change_reason
• FROM apps.hrfv_salaries
• WHERE pay_basis = 'Annual'
• AND salary_change_date >= SYSDATE - 365
• ORDER BY salary_change_date DESC;

A second common pattern aggregates average comparatio by grade to support equity analysis: SELECT grade_rate_basis, AVG(grade_comparatio) FROM apps.hrfv_salaries GROUP BY grade_rate_basis;. Note that several columns (ABSOLUTE_INCREMENT, PERCENTAGE_INCREMENT, PREV_PAY_BASIS) are deliberately NULL placeholders in the template and should not be relied upon without validation against the deployed 12.1.1 or 12.2.2 instance.