Search Results source_start_date




Overview
Explore in AI Chat

Overview

PAY_ELEMENT_ENTRIES_F is the core dated (effective-dated) table in the Oracle Payroll (PAY) product that stores the list of element entries associated with each assignment. In Oracle EBS 12.1.1 and 12.2.2, an "element entry" is a specific instance of an earnings or deduction element (for example, Salary, Bonus, or a voluntary deduction) assigned to an employee's assignment for a defined effective period. Every recurring or one-time pay component processed during a payroll run ultimately traces back to a row in this table.

The table resides in the HR schema and holds 89 documented columns. Its primary key, PAY_ELEMENT_ENTRIES_F_PK, is composed of ELEMENT_ENTRY_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE, reflecting the datetracked nature of the entity. From a Data Vault modeling perspective, the metadata's heuristic classification is link, because the table principally represents a relationship between an assignment, an element link, and the associated element definition. Practitioners building a warehouse layer may alternatively treat it as a satellite if the emphasis is on the descriptive attributes of the element entry over time.

Key Information Stored

The most business-relevant columns include:

The surrogate key (ELEMENT_ENTRY_ID) uniquely identifies the logical entry, while the unique index PAY_ELEMENT_ENTRIES_F_PK enforces the datetracked business key across the three primary key columns.

Common Use Cases and Queries

Typical reporting scenarios include listing all active entries for an assignment, reconciling entries processed in a payroll run, auditing cost allocation assignments, and tracing the assignment action that created an entry. A common query pattern retrieves current entries for a given assignment:

  • SELECT element_entry_id, assignment_id, element_link_id, element_type_id, effective_start_date, effective_end_date FROM pay_element_entries_f WHERE assignment_id = :p_assignment_id AND SYSDATE BETWEEN effective_start_date AND effective_end_date;
  • Joining to PAY_COST_ALLOCATION_KEYFLEX via COST_ALLOCATION_KEYFLEX_ID to report cost distribution.
  • Joining to PAY_ASSIGNMENT_ACTIONS via UPDATING_ACTION_ID to audit the originating personnel action.
  • Filtering on ENTRY_INFORMATION_CATEGORY to extract flexfield values for downstream reporting.

Because the table is datetracked, queries must always apply an effective date predicate to avoid returning historical versions.

Related Objects

  • PAY_COST_ALLOCATION_KEYFLEX — Referenced via PAY_ELEMENT_ENTRIES_F.COST_ALLOCATION_KEYFLEX_ID.
  • PAY_ASSIGNMENT_ACTIONS — Referenced via PAY_ELEMENT_ENTRIES_F.UPDATING_ACTION_ID.
  • PAY_ELEMENT_ENTRIES_F_PK — The primary key index on ELEMENT_ENTRY_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE.
  • PAY_ELEMENT_LINKS_F — Provides the element link definition joined by ELEMENT_LINK_ID.
  • PAY_ELEMENT_TYPES_F — Provides the element definition joined by ELEMENT_TYPE_ID.
  • PER_ALL_ASSIGNMENTS_F — The assignment master table joined by ASSIGNMENT_ID.

These relationships make PAY_ELEMENT_ENTRIES_F a central link between workforce assignments, element configuration, and payroll cost allocation in Oracle Payroll.