Search Results multiple_components

Overview

The view HRIFV_SALPREV_PRO belongs to the HRI – Human Resources Intelligence product family, a legacy Oracle EBS reporting layer historically shipped with the HRMS/HR Intelligence module. Its name follows the HRI naming convention (HRIFV_...), indicating that it is a "Human Resources Intelligence Function View" intended to expose flattened, denormalized human resources data for analytical reporting rather than for transactional use. The view presents proposed salary information for employee assignments, combining assignment-level attributes with salary proposal details, pay basis definitions, payroll elements, and foreign-key resolutions into a single, query-friendly structure.

The ETRM metadata documents HRIFV_SALPREV_PRO as Obsolete and notes that it is Not implemented in this database. The view text carries the header comment $HEADER: HRIVIEW.LDT 115.3 2001/09/18 10:51:35 PKM SHIP $, confirming its release with the original HR Intelligence delivery. Because it is obsolete, it should be treated as a reference artifact; organizations on EBS 12.1.1 or 12.2.2 will generally migrate equivalent logic into custom queries or BI Publisher reports against base HRMS tables.

The user's search term working_hours_amount maps directly to a column exposed by this view, resolved from PER_ASSIGNMENTS_F.NORMAL_HOURS. This indicates the search targeted assignment working-hours data as surfaced through the salary proposal view.

Underlying Base Objects

Although the ETRM referenced-object list is empty, the view text documents its source tables explicitly. The principal base object is PER_ASSIGNMENTS_F (aliased ASG), joined to PER_PAY_BASES (PPB), PER_PAY_PROPOSALS (PRO and PRO_NEXT), and PER_ELEMENT_TYPES (PET, inferred from the OUTPUT_CURRENCY_CODE reference). A business group table provides BUSINESS_GROUP_NAME. The view also calls the database function HR_BIS.BIS_DECODE_LOOKUP to translate lookup codes such as PAY_BASIS and YES_NO into their descriptive meanings, and HR_GENERAL.END_OF_TIME to supply an open-ended high date.

The PRO_NEXT self-join on PER_PAY_PROPOSALS establishes the effective date range: each proposal's EFFECTIVE_TO_DATE is derived as the next proposal's CHANGE_DATE minus one day, yielding a contiguous history of salary proposals per assignment.

Key Columns

• BUSINESS_GROUP_NAME – enterprise business group owning the assignment.
• ASSIGNMENT_NUMBER – the employee assignment identifier.
• SALARY_AMOUNT – PRO.PROPOSED_SALARY_N, the numeric proposed salary.
• ANNUALIZATION_FACTOR / ANNUAL_SALARY – the pay annualization factor and its product with the proposed salary.
• CURRENCY / CURRENCY_CODE – output currency resolved from the element type.
• EFFECTIVE_FROM_DATE / EFFECTIVE_TO_DATE / EFFECTIVE_TO_DATE_NN – proposal validity window; the _NN variant substitutes HR_GENERAL.END_OF_TIME for open records.
• WORKING_HOURS_AMOUNT – ASG.NORMAL_HOURS, the assignment's normal working hours, and the column matching the user's search.
• WORKING_HOURS_FREQUENCY – ASG.FREQUENCY, the period for the working hours.
• PAYROLL / PAYROLL_ID – payroll to which the assignment is attached.
• PAY_BASIS / PAY_BASIS_CODE – descriptive and coded pay basis values.
• RANKING, MULTIPLE_COMPONENTS, SALARY_BASIS – proposal ranking, multi-component indicator, and pay basis name.
• Identifier columns – ASSIGNMENT_ID, PERSON_ID, BUSINESS_GROUP_ID, ORGANIZATION_ID, LOCATION_ID, JOB_ID, GRADE_ID, POSITION_ID, PAY_PROPOSAL_ID, PERFORMANCE_REVIEW_ID, EVENT_ID, PAY_BASIS_ID, INPUT_VALUE_ID, RATE_ID, ELEMENT_TYPE_ID.

Common Use Cases and Queries

Typical usage centres on salary-proposal analysis: comparing proposed versus annualized salary, checking working-hours assumptions for a proposal, and assembling effective-dated histories of proposed pay by assignment, organization, job, or grade.

A sample query retrieving proposal salary and working hours for a person:

SELECT business_group_name,
       assignment_number,
       salary_amount,
       annual_salary,
       currency,
       working_hours_amount,
       working_hours_frequency,
       effective_from_date,
       effective_to_date
FROM   hrifv_salprev_pro
WHERE  assignment_number = :p_assignment_number
ORDER  BY effective_from_date;

Because the view is obsolete and absent from current databases, practitioners should reproduce its logic directly against PER_ASSIGNMENTS_F, PER_PAY_PROPOSALS, and PER_PAY_BASES, preserving the NORMAL_HOURS derivation for working_hours_amount and the PRO_NEXT self-join for effective dating when building replacement reports.