Search Results pay_element_entry_values

Overview

PAY_ELEMENT_ENTRY_VALUES is a date-effective (or "date-tracked") view owned by the APPS schema within the Oracle Payroll (PAY) module. Its purpose is to expose only those element entry value records that are valid as of the current application session's effective date. Rather than presenting every historical or future-dated row stored on the underlying table, the view applies a runtime filter so that callers see a single, session-consistent slice of the data. This makes the object particularly valuable for payroll reporting, concurrent programs, and integrations that must respect the effective dating conventions used throughout Oracle EBS Human Resources and Payroll. Because the filtering is driven by the session effective date rather than the system date, the view behaves correctly for backdated or future-dated transactions and for users who change their effective date within a session. The view is documented as VALID in ETRM for the 12.1.1 and 12.2.2 releases and is classified as a date-effective view, indicating that date-tracked (datetrack) logic governs which rows are returned.

Underlying Base Objects

According to the documented view text, PAY_ELEMENT_ENTRY_VALUES is defined over a single base object: PAY_ELEMENT_ENTRY_VALUES_F, referenced through a SYNONYM in the APPS schema. The _F suffix confirms this is the datetracked ("frozen" effective-dated) table that physically holds all versions of each element entry value. The view additionally references FND_SESSIONS, also via a SYNONYM, solely to derive the current effective date. No joins to other application tables are present in the documented definition, so the view's column set mirrors the selected columns of the base table exactly and introduces no new attributes.

Key Columns

The view exposes the following documented columns:

• ELEMENT_ENTRY_VALUE_ID — Primary identifier for the element entry value record.
• EFFECTIVE_START_DATE — The date from which this version of the record becomes effective (datetrack start).
• EFFECTIVE_END_DATE — The date through which this version remains effective (datetrack end).
• INPUT_VALUE_ID — Foreign reference to the element input value (the specific input for which a value is being captured).
• ELEMENT_ENTRY_ID — Foreign reference to the parent element entry to which this value belongs.
• SCREEN_ENTRY_VALUE — The value captured for the input, as represented on the element entry screen (commonly stored as a character value and later converted according to the input's data type).

Together these columns define the value supplied to a given input of a given element entry, scoped to the effective-dated period during which that value applies.

Common Use Cases and Queries

Typical scenarios include auditing element entry values for a supplied date, joining entry values to their parent entries and element definitions for reporting, and driving interfaces that export payroll inputs. A representative query is:

SELECT eev.element_entry_value_id,
       eev.element_entry_id,
       eev.input_value_id,
       eev.screen_entry_value,
       eev.effective_start_date,
       eev.effective_end_date
FROM   apps.pay_element_entry_values eev
WHERE  eev.element_entry_id = :p_element_entry_id;

Because the view already restricts rows to the session effective date, it is generally preferable to query it rather than the underlying _F table, unless historical or future-dated rows are explicitly required. To inspect all datetracked versions, query PAY_ELEMENT_ENTRY_VALUES_F directly. Note that results depend on the caller's session effective date, so integrations should set the effective date intentionally before relying on the view's output.