Results for “annualized_hours”

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

Overview

APPS.PER_PAY_PROPOSALS_V is a Human Resources (PER) view that consolidates employee salary proposal and performance review information into a single, denormalized reporting structure. It is owned by the APPS schema and carries a VALID status in both Oracle EBS 12.1.1 and 12.2.2. The view joins the transactional proposal table PER_PAY_PROPOSALS with a series of descriptive lookup and setup tables, resolving coded identifiers (proposal reason, performance rating, event type, pay basis, rate basis) into their translatable meanings. Because it is defined with outer joins ((+) syntax) against the HR_LOOKUPS views, a proposal row is preserved even when no matching lookup exists. The view thereby serves as the canonical read-only interface for salary proposals, merit/market adjustments, and associated performance ratings, and is commonly the target of HR analytics extracts, concurrent-program reports, and downstream integrations that must not query the base tables directly.

Underlying Base Objects

The view is defined over a wide set of documented base objects. The driving table is PER_PAY_PROPOSALS (accessed via synonym), aliased PRO, which supplies the proposal identity, dates, salary figures, and descriptive flexfield columns. Supporting PER objects include PER_EVENTS (EVT), PER_ALL_ASSIGNMENTS_F (ASG), and PER_PAY_BASES (PPB), the latter supplying the PAY_BASIS and RATE_BASIS attributes. Payroll setup and element detail is drawn from PAY_ELEMENT_ENTRIES_F (PEE), PAY_ELEMENT_TYPES_F (PET), PAY_ELEMENT_TYPES_F_TL (PETTL), and PAY_INPUT_VALUES_F (PIV). Descriptive text is resolved through HR_LOOKUPS (HLU, HLU2, HLU3) and HR_LOCATIONS (LOC). Documented ETRM metadata also lists the packages HR_API, HR_GENERAL, and HR_SECURITY as referenced objects; HR_GENERAL.DECODE_LOOKUP is invoked in the SELECT list, and HR_SECURITY applies the row-level security predicate that restricts results to the querying user's authorized business groups and assignments. The synonym-to-view mapping (PAY_* and PER_* synonyms resolving to the underlying _F, _TL, and assignment views) is significant because date-tracked objects such as PER_ALL_ASSIGNMENTS_F and PAY_ELEMENT_ENTRIES_F require an effective-date context for correct results.

Key Columns

• PAY_PROPOSAL_ID, ROWID — primary identifiers for the proposal row.
• BUSINESS_GROUP_ID, ASSIGNMENT_ID — organizational and employee context; used by HR_SECURITY filtering.
• PROPOSED_SALARY_N — the proposed salary amount, exposed through TO_CHAR.
• REVIEW_DATE / DATE_START — the effective review date, coalesced from the event start date and the proposal review date.
• PROPOSAL_REASON and its MEANING — the coded reason and its decoded lookup value.
• PERFORMANCE_RATING and its MEANING — the rating code plus decoded description.
• PAY_BASIS and RATE_BASIS — the pay and rate basis codes from PER_PAY_BASES, with PAY_BASIS additionally decoded via DECODE_LOOKUP('PAY_BASIS', ...); RATE_BASIS is the column most frequently targeted by users searching on "rate_basis" and identifies the unit of measure against which a rate is expressed (for example hourly, weekly, or annual).
• ANNUALIZED_HOURS — the standard hours used to annualize a rate.
• ELEMENT_NAME, ELEMENT_TYPE_ID, INPUT_VALUE_ID, UOM, ELEMENT_ENTRY_ID — payroll element and input value linkage.
• APPROVED, MULTIPLE_COMPONENTS, OBJECT_VERSION_NUMBER — workflow and concurrency control attributes.
• ATTRIBUTE1 through ATTRIBUTE20, ATTRIBUTE_CATEGORY — descriptive flexfield columns.
• Audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include merit-cycle reporting, compensation analysis, and feeds to third-party payroll or HR systems. Because the view is secured, queries should supply an effective date and rely on HR_SECURITY to scope results.

Retrieving proposals with rate basis detail for an employee:

SELECT assignment_id,
       review_date,
       proposed_salary_n,
       pay_basis,
       rate_basis,
       annualized_hours
  FROM apps.per_pay_proposals_v
 WHERE assignment_id = :p_assignment_id
   AND review_date BETWEEN :p_start AND :p_end
 ORDER BY review_date;

Aggregating proposals by rate basis for a compensation review:

SELECT rate_basis,
       COUNT(*) proposals,
       SUM(TO_NUMBER(proposed_salary_n)) total_salary
  FROM apps.per_pay_proposals_v
 WHERE business_group_id = :p_bg_id
   AND approved = 'Y'
 GROUP BY rate_basis;

Joining to decoded reasons and ratings for a merit report:

SELECT a.employee_number,
       v.proposed_salary_n,
       v.meaning proposal_reason,
       v.performance_rating
  FROM apps.per_pay_proposals_v v,
       apps.per_all_assignments_f a
 WHERE v.assignment_id = a.assignment_id
   AND TRUNC(SYSDATE) BETWEEN a.effective_start_date AND a.effective_end_date;

These patterns illustrate the view's role as a governed, decode-enriched access point for salary proposal data, with RATE_BASIS available for rate normalization across payroll elements.