Search Results rating_meaning




Overview
Explore in AI Chat

Overview

APPS.PER_PAY_PROPOSALS_V2 is a supplementary Oracle E-Business Suite view owned by the APPS schema and registered in FND Design Data as PER.PER_PAY_PROPOSALS_V2. It belongs to the Oracle Human Resources (PER) product family and is classified as a "supplementary view used to simplify forms coding." Oracle explicitly warns that this view is not intended for direct customer querying or DML, and that its definition may change dramatically across minor or major releases. Consequently, it should be treated as a forms-support artifact rather than a stable public API.

Functionally, the view exposes salary and compensation proposal data — proposed salary amounts, performance ratings, proposal reasons, review dates, and descriptive Flexfield attributes — joined to lookup meanings so that Oracle Forms can render decoded values without additional programmatic lookups. The presence of the RATING_MEANING column, which is the attribute referenced in the user's search, reflects the view's practice of resolving coded lookup values (such as performance rating codes) into their human-readable meanings for display in the Pay Proposals form.

Underlying Base Objects

Per the ETRM metadata, the view is defined over the following documented base objects:

The view therefore joins proposal data with review and lookup metadata, producing a forms-ready projection.

Key Columns

Common Use Cases and Queries

Because Oracle discourages querying this view directly, the recommended practical approach is to read the same data from PER_PAY_PROPOSALS joined to HR_LOOKUPS, thereby avoiding exposure to view changes. A representative (read-only) query resembling the view's intent is:

  • SELECT ppp.pay_proposal_id, ppp.performance_rating, hl.meaning rating_meaning, ppp.proposed_salary
  • FROM per_pay_proposals ppp, hr_lookups hl
  • WHERE hl.lookup_type = 'PERFORMANCE_RATING'
  • AND hl.lookup_code = ppp.performance_rating;

Typical scenarios include reviewing historical salary proposals alongside rated performance outcomes, reconciling approved versus pending proposals, and validating Flexfield attribute values. Where rating_meaning is required, always join to HR_LOOKUPS to guarantee the correct lookup type and language.