Search Results per_pay_proposals_v2




Overview
Explore in AI Chat

Overview

APPS.PER_PAY_PROPOSALS_V2 is a valid database view in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, owned by the APPS schema and assigned to the PER (Human Resources) product family. According to the ETRM metadata, its documented purpose is "Used to support user-interface" — meaning it exists primarily to drive Oracle Forms-based and OAF-based compensation and salary administration pages rather than to serve as a public reporting interface. The V2 suffix indicates that it is a revised version of the original pay proposal view, introduced to expose additional attributes required by the Salary Administration and Compensation Workbench user interfaces.

Because the view flattens several disparate sources — pay proposals, performance reviews, and code-translated lookups — into a single denormalized result set, it is frequently encountered by developers and administrators who trace the SQL behind the "Manage Salary Proposals" and pay proposal entry screens. Users searching for the column forced_ranking will find it here, exposed directly from the underlying PER_PAY_PROPOSALS table.

Underlying Base Objects

The view is defined over the following documented base objects:

Both lookup joins are outer joins, and the performance review join is likewise outer (PRV.PERFORMANCE_REVIEW_ID(+)), so pay proposals are returned even when no associated review or lookup translation exists.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing forced rankings, reporting proposed salary changes by business group, and reconciling performance ratings against proposals.

SELECT pay_proposal_id, assignment_id, forced_ranking,
       proposed_salary_n, rating_meaning, reason_meaning
FROM   apps.per_pay_proposals_v2
WHERE  business_group_id = :p_bg_id
AND    forced_ranking IS NOT NULL
ORDER  BY forced_ranking;

To trace salary proposals awaiting approval:

SELECT pay_proposal_id, assignment_id, proposed_salary_n, approved
FROM   apps.per_pay_proposals_v2
WHERE  approved = 'N';

Because the view is documented as a user-interface support object, Oracle does not guarantee it as a stable public API; custom reports should ideally reference PER_PAY_PROPOSALS directly, using PER_PAY_PROPOSALS_V2 primarily for read-only inspection and diagnostics.