Search Results pay_element_entry_values_f_pk




Overview
Explore in AI Chat

Overview

The HR.PAY_ELEMENT_ENTRY_VALUES_F table is a core DateTracked table within the Oracle E-Business Suite (EBS) Human Resources (HR) and Payroll modules, specifically versions 12.1.1 and 12.2.2. It functions as the definitive repository for the actual data values entered for an employee's element entries. An element, such as Overtime or Bonus, is defined with one or more input values (e.g., Hours, Amount). This table stores the specific, user-entered or system-calculated data (like "8" for hours worked) that corresponds to a particular input value for a specific element entry over a defined period. Its DateTracked nature, managed via EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, allows for the accurate historical tracking of value changes over time, which is critical for payroll calculations and audit trails.

Key Information Stored

The table's structure is designed to link entry values to their defining metadata and the parent entry. Key columns include:

  • ELEMENT_ENTRY_VALUE_ID: The system-generated unique identifier and part of the primary key.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE: Define the date range for which the stored SCREEN_ENTRY_VALUE is valid. These columns complete the primary key (PAY_ELEMENT_ENTRY_VALUES_F_PK) alongside ELEMENT_ENTRY_VALUE_ID.
  • INPUT_VALUE_ID: Foreign key to PAY_INPUT_VALUES, identifying which element input value (e.g., "Hours," "Rate") this record pertains to.
  • ELEMENT_ENTRY_ID: Foreign key to PAY_ELEMENT_ENTRIES_F, linking this value to the specific instance of an element assigned to an employee.
  • SCREEN_ENTRY_VALUE: The actual entered or derived value stored as a VARCHAR2, which the payroll engine interprets based on the linked input value's definition.

Common Use Cases and Queries

This table is central to payroll data validation, historical reporting, and troubleshooting. A common use case is auditing the values used in a payroll run for a specific employee's element. The primary key relationship is crucial for accurate queries, as a single ELEMENT_ENTRY_VALUE_ID can have multiple DateTracked rows. A typical query to retrieve all current entry values for a specific element entry would leverage the EFFECTIVE_END_DATE.

Sample Query:
SELECT iv.NAME, peevf.SCREEN_ENTRY_VALUE, peevf.EFFECTIVE_START_DATE, peevf.EFFECTIVE_END_DATE
FROM hr.pay_element_entry_values_f peevf,
     hr.pay_input_values iv
WHERE peevf.ELEMENT_ENTRY_ID = :p_element_entry_id
  AND peevf.INPUT_VALUE_ID = iv.INPUT_VALUE_ID
  AND SYSDATE BETWEEN peevf.EFFECTIVE_START_DATE AND peevf.EFFECTIVE_END_DATE
ORDER BY iv.NAME;

For reporting gross-to-net calculations, this table is joined through PAY_ELEMENT_ENTRIES_F to employee and element definition tables to trace the source of calculated pay.

Related Objects

The table maintains defined foreign key relationships and is referenced by other application objects, forming a critical part of the payroll data model.

  • Primary Key: PAY_ELEMENT_ENTRY_VALUES_F_PK (ELEMENT_ENTRY_VALUE_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE).
  • Foreign Key (PAY_INPUT_VALUES): The INPUT_VALUE_ID column references PAY_INPUT_VALUES.INPUT_VALUE_ID, linking the stored data to its definition.
  • Foreign Key (PAY_ELEMENT_ENTRIES_F): The ELEMENT_ENTRY_ID column references PAY_ELEMENT_ENTRIES_F.ELEMENT_ENTRY_ID, connecting the value to the parent entry.
  • Indexes: Non-unique indexes on INPUT_VALUE_ID (N1) and ELEMENT_ENTRY_ID with effective dates (N50) optimize performance for common access paths.
  • Referencing Objects: Per the dependencies, the table is referenced by database triggers (e.g., GHR_PAY_ELEMENT_ENTVAL_F_AFIUD) and public synonyms (PAY_ELEMENT_ENTRY_VALUES_F), indicating its use by both base Payroll and extensions like Federal Human Resources (GHR).