Search Results pay_element_entries_f

Overview

The PAY_ELEMENT_ENTRIES_F table is a core data object within the Oracle E-Business Suite Payroll module (PAY). It functions as the master repository for all recurring and non-recurring element entries linked to employee assignments. An element entry represents the specific instance of a compensation or deduction element, such as a salary, bonus, or tax withholding, assigned to an employee. This table is date-tracked, as indicated by the "_F" suffix and the EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns, enabling the maintenance of a complete history of entry changes over time. Its primary role is to store the definitive list of active and historical earnings and deductions that are processed during payroll calculations, making it fundamental to the payroll engine's operation.

Key Information Stored

The table's structure is designed to manage the lifecycle and context of each element entry. The primary key is a composite of ELEMENT_ENTRY_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE, ensuring unique identification of each entry version. The ELEMENT_ENTRY_ID itself uniquely identifies the entry across all its date-effective versions. Critical foreign key columns establish essential relationships: the ASSIGNMENT_ID links the entry to a specific employee assignment in PER_ALL_ASSIGNMENTS_F, and the ELEMENT_LINK_ID connects it to the specific element and its eligibility rules defined in PAY_ELEMENT_LINKS_F. Other significant columns include the ENTRY_TYPE (e.g., 'E' for standard entry), the COST_ALLOCATION_KEYFLEX_ID for assigning costs, and the UPDATING_ACTION_ID, which tracks the payroll run or process that last modified the entry.

Common Use Cases and Queries

This table is central to payroll reporting, auditing, and data validation. Common use cases include generating a report of all element entries for an employee to verify compensation setup, auditing changes to specific entries over time, and identifying entries with certain characteristics (e.g., all entries of a particular element type) for mass updates or corrections. A typical query to retrieve current active entries for an assignment would join to PER_ALL_ASSIGNMENTS_F and PAY_ELEMENT_LINKS_F, filtering on SYSDATE between the effective dates.

SELECT pee.element_entry_id,
       pee.assignment_id,
       pel.element_type_id,
       pee.effective_start_date,
       pee.effective_end_date
FROM   pay_element_entries_f pee,
       pay_element_links_f pel
WHERE  pee.assignment_id = :p_assignment_id
AND    SYSDATE BETWEEN pee.effective_start_date AND pee.effective_end_date
AND    pee.element_link_id = pel.element_link_id
AND    SYSDATE BETWEEN pel.effective_start_date AND pel.effective_end_date;

Related Objects

PAY_ELEMENT_ENTRIES_F has integral relationships with several other key payroll tables, as indicated by its foreign key constraints. It is a primary child table of PAY_ASSIGNMENT_ACTIONS via the UPDATING_ACTION_ID column, linking each entry modification to a specific payroll calculation action. It also references PAY_COST_ALLOCATION_KEYFLEX through COST_ALLOCATION_KEYFLEX_ID for accounting cost distribution. Crucially, it is joined to PAY_ELEMENT_LINKS_F (on ELEMENT_LINK_ID) to retrieve the element type and rules, and to PER_ALL_ASSIGNMENTS_F (on ASSIGNMENT_ID) to get employee and assignment details. For processing, it feeds into tables like PAY_RUN_RESULTS which store the calculated values for each entry per payroll run.