Search Results approved_code

Overview

HRIFV_SAL_PRO is an APPS-owned view within the Oracle E-Business Suite 12.1.1 / 12.2.2 environment, historically associated with the HRI — Human Resources Intelligence product. HRI is documented as obsolete, which means the object is retained for backward compatibility and reference rather than active product development. The view exposes salary information derived from salary proposals, presented within an effective date range. In practical terms, each row describes a proposed salary amount for a person and assignment, together with the period over which that proposal is effective.

The view functioned as a reporting and integration surface for HR intelligence extract processes. Rather than forcing consumers to assemble salary, assignment, payroll, and currency context from multiple base tables, HRIFV_SAL_PRO consolidates those attributes into a single denormalized result set suitable for downstream analytics, HR data warehouses, or interface extracts.

Underlying Base Objects

The view is defined over several documented base objects, with the principal driver being PER_PAY_PROPOSALS (aliased PRO), which supplies the proposed salary, change date, approval flag, ranking, and multiple-components indicator. The person context comes from PER_ALL_PEOPLE_F (PEO), assignment context from PER_ASSIGNMENTS_F (ASG), and business group naming from HR_ALL_ORGANIZATION_UNITS_TL (BGRT).

• PER_PAY_BASES (PPB) provides pay basis, annualization factors, grade annualization, and the salary basis name.
• PAY_PAYROLLS_F (PAY) contributes the payroll name and identifier.
• PAY_ELEMENT_TYPES_F and PAY_INPUT_VALUES_F support element and input value resolution.
• PER_PERIODS_OF_SERVICE, PER_TIME_PERIOD_TYPES, and currency context (PET) supply service periods, fiscal period counts, and output currency.
• HR_BIS, HR_GENERAL, and HR_SECURITY are database packages invoked for lookup decoding and end-of-time handling.

The view text references HR_BIS.BIS_DECODE_LOOKUP for code-to-meaning translation and HR_GENERAL.END_OF_TIME as a boundary value, indicating its dependency on these packages at runtime.

Key Columns

• BUSINESS_GROUP_NAME, PERSON_NAME, EMPLOYEE_NUMBER, ASSIGNMENT_NUMBER — entity-level identification attributes.
• SALARY_AMOUNT — the proposed salary value (PROPOSED_SALARY_N).
• ANNUALIZATION_FACTOR, GRADE_ANNUALIZATION_FACTOR, ANNUAL_SALARY — derived annualized compensation values.
• CURRENCY / CURRENCY_CODE — the output currency code from PET.
• EFFECTIVE_FROM_DATE, EFFECTIVE_TO_DATE — the salary proposal validity range; the non-null variant uses END_OF_TIME when no subsequent change exists.
• APPROVED / APPROVED_CODE — the approval indicator. APPROVED_CODE returns the raw PRO.APPROVED value, while APPROVED applies BIS_DECODE_LOOKUP('YES_NO', ...) to render a readable meaning. The approved_code term that led to this search resolves to this column.
• PAY_BASIS / PAY_BASIS_CODE, MULTIPLE_COMPONENTS / MULTIPLE_COMPONENTS_CODE — paired coded and decoded indicators.
• RANKING, SALARY_BASIS, WORKING_HOURS_AMOUNT, WORKING_HOURS_FREQUENCY, PAYROLL — supporting compensation and payroll context.
• ASSIGNMENT_ID, PERSON_ID, BUSINESS_GROUP_ID, ORGANIZATION_ID, LOCATION_ID, JOB_ID, GRADE_ID, POSITION_ID, PAYROLL_ID — key identifiers for joining and extraction.

Common Use Cases and Queries

Typical usage includes extracting approved salary proposals over an as-of date, feeding HR compensation reports, and reconciling proposal history per assignment. A representative query filtering on the approved flag:

• SELECT person_name, employee_number, salary_amount, annual_salary, currency, effective_from_date, effective_to_date FROM apps.hrifv_sal_pro WHERE approved_code = 'Y';
• SELECT person_id, assignment_id, salary_amount, effective_from_date FROM apps.hrifv_sal_pro WHERE TRUNC(SYSDATE) BETWEEN effective_from_date AND effective_to_date_nn;
• SELECT business_group_name, payroll, pay_basis, COUNT(*) FROM apps.hrifv_sal_pro GROUP BY business_group_name, payroll, pay_basis;

Because the view resolves security through HR_SECURITY and depends on multiple synonyms and packages, consumers should confirm that APPS synonyms and HR security profiles are correctly configured. Given its obsolete HRI lineage, the view should be treated as a legacy reporting object on 12.1.1 and 12.2.2.