Search Results per_pay_proposal_components

Overview

The PER_PAY_PROPOSAL_COMPONENTS table is a core data object within the Oracle E-Business Suite (EBS) Payroll module (PAY). It stores the detailed, line-item components that constitute a pay proposal for an employee's assignment. A pay proposal represents a recommended or approved change to an employee's compensation. This table breaks down that overall proposal into its constituent parts, such as base salary adjustments, bonus amounts, or other earnings components, each potentially with its own justification and effective details. Its role is to provide granularity and auditability for compensation changes, enabling complex salary structures to be managed and tracked over time within the HRMS system.

Key Information Stored

Based on the provided ETRM metadata, the table's structure centers on a unique component identifier and its relationship to a parent proposal. The primary key is COMPONENT_ID, ensuring each component record is unique. The PAY_PROPOSAL_ID column is a foreign key that links the component to its overarching pay proposal in the PER_PAY_PROPOSALS table. The COMPONENT_REASON column is part of a unique key constraint (UK2) alongside PAY_PROPOSAL_ID, indicating that within a single proposal, the reason for a component must be distinct. The documented foreign key to HR_ALL_ORGANIZATION_UNITS via BUSINESS_GROUP_ID anchors the data within the correct organizational and security context. Typical columns not listed in the excerpt but standard for such a table would include COMPONENT_TYPE (e.g., 'Salary', 'Bonus'), AMOUNT or VALUE, CURRENCY_CODE, and EFFECTIVE_DATE.

Common Use Cases and Queries

This table is central to compensation analysis and historical reporting. A common use case is generating a detailed audit report of all compensation changes for an employee or a group of employees within a specific period. Another is analyzing the breakdown of a specific pay proposal to understand its composition. A typical query would join PER_PAY_PROPOSAL_COMPONENTS to PER_PAY_PROPOSALS and PER_ALL_PEOPLE_F to retrieve component details with employee information.

• Sample Query: To find all salary component proposals for an employee in a given year:
  SELECT ppc.* FROM per_pay_proposal_components ppc, per_pay_proposals pp WHERE ppc.pay_proposal_id = pp.pay_proposal_id AND pp.assignment_id = &assignment_id AND pp.change_date BETWEEN TO_DATE('01-JAN-2023','DD-MON-YYYY') AND TO_DATE('31-DEC-2023','DD-MON-YYYY') AND ppc.component_type = 'Salary';
• Reporting: The table serves as a primary source for custom reports on compensation history, budget impact analysis of proposed raises, and tracking the frequency and value of different component types (e.g., bonuses, allowances).

Related Objects

The ETRM documentation explicitly defines the following key relationships for the PER_PAY_PROPOSAL_COMPONENTS table:

• Parent Table (PER_PAY_PROPOSALS): The primary relationship is via the foreign key column PAY_PROPOSAL_ID. This links each component row to its parent pay proposal record, which contains higher-level information like the assignment identifier, proposal status, and overall change date.
• Reference Table (HR_ALL_ORGANIZATION_UNITS): A foreign key relationship exists via the BUSINESS_GROUP_ID column. This enforces data integrity and secures the component data within the correct business group context, a fundamental security and multi-organization principle in Oracle EBS HRMS.

In practice, this table is also closely related to core HR tables like PER_ALL_PEOPLE_F and PER_ALL_ASSIGNMENTS_F, typically accessed via joins through the PER_PAY_PROPOSALS table.