Results for “forced_ranking”

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

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:

• PER_PAY_PROPOSALS (SYNONYM) — the primary driving table, aliased PRO, supplying the majority of columns including FORCED_RANKING, PROPOSED_SALARY_N, PROPOSAL_REASON, APPROVED, COMMENTS, and the descriptive flexfield attributes.
• PER_PERFORMANCE_REVIEWS (SYNONYM) — aliased PRV, joined on PERFORMANCE_REVIEW_ID and providing PERFORMANCE_RATING and REVIEW_DATE.
• HR_LOOKUPS (VIEW) — joined twice with outer joins (HL1 and HL2) to translate PROPOSAL_REASON into REASON_MEANING and PERFORMANCE_RATING into RATING_MEANING via the lookup types 'PROPOSAL_REASON' and 'PERFORMANCE_RATING' respectively.
• HR_API (PACKAGE) — referenced by the compensation business logic that populates and maintains the underlying records.

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

• PAY_PROPOSAL_ID — surrogate primary key of the proposal record; ROW_ID is also returned for Forms locking.
• ASSIGNMENT_ID / BUSINESS_GROUP_ID — identify the employee assignment and the HR business group.
• FORCED_RANKING — the ranking value assigned to the proposal, typically used in forced-distribution or forced-ranking compensation models to order employees for merit allocation.
• PROPOSED_SALARY (TO_CHAR) and PROPOSED_SALARY_N (numeric) — the proposed new salary, exposed in both character and numeric form to suit different UI widgets.
• PERFORMANCE_RATING / RATING_MEANING and PROPOSAL_REASON / REASON_MEANING — coded value plus translated lookup meaning.
• CHANGE_DATE, LAST_CHANGE_DATE, NEXT_SAL_REVIEW_DATE, REVIEW_DATE — effective and review timing attributes.
• MULTIPLE_COMPONENTS, APPROVED, COMMENTS — workflow/approval and component flagging.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–20 — the descriptive flexfield segments.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — standard WHO audit 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.