Results for “pay_element_entries_x”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PAY_ELEMENT_ENTRIES_X is a date-effective (public) view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the PAY — Payroll product family and, per ETRM metadata, is documented as a "Date-effective view." The view exposes element entry records that are valid as of the current system date, providing a runtime-filtered projection of the underlying element entry entity.

The distinguishing characteristic of PAY_ELEMENT_ENTRIES_X is its WHERE predicate: TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE. This means the view returns only those element entry rows whose effective date range encompasses the current date, applying the TRUNC function to SYSDATE so that time-of-day components do not affect the comparison. It is the standard Oracle date-effective (the "_X" suffix) convention used throughout Oracle HRMS and Payroll, in contrast to the "_F" (frozen/base) view that exposes all dated rows regardless of currency.

Because it filters by SYSDATE, the view is inherently non-deterministic across days; the same query can return a different result set tomorrow. This makes it well suited for real-time payroll processing, concurrent program logic, and operational reporting, but unsuitable as a source for historical point-in-time extracts, which should reference the base table or a date-bound query instead.

Underlying Base Objects

The view is defined over a single documented base object: PAY_ELEMENT_ENTRIES_F, referenced via a synonym in the APPS schema. PAY_ELEMENT_ENTRIES_F is the "frozen" or base table that physically stores element entry rows along with their EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns, which together implement the datetrack/date-effective model. The "_X" view does not add joins to other tables; it is a straight column projection of the _F table with the date-effective filter applied. All columns listed in the ETRM view text — ELEMENT_ENTRY_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, ASSIGNMENT_ID, ELEMENT_LINK_ID, and the ENTRY_INFORMATION1..30 and ATTRIBUTE1..20 descriptive flexfield columns — originate directly from PAY_ELEMENT_ENTRIES_F. Consequently, any DML or drill-down that must see future-dated or expired entries should target the _F object rather than this view.

Key Columns

• ELEMENT_ENTRY_ID — Primary identifier for the element entry; the key used to relate entries to their source link, assignment, and cost allocations.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — The datetrack boundaries that drive the view's SYSDATE filter.
• ASSIGNMENT_ID — The employee assignment to which the entry applies.
• ELEMENT_LINK_ID — The element link that determines eligibility and input values for the entry.
• ORIGINAL_ENTRY_ID / TARGET_ENTRY_ID — Traceability columns linking an entry to the entry it was created from or converted into.
• ENTRY_TYPE / CREATOR_TYPE / CREATOR_ID / REASON — Classify how and by whom the entry was created and why (for example, manual entry versus a system-generated adjustment).
• COST_ALLOCATION_KEYFLEX_ID — Reference to the cost allocation key flexfield used to distribute the entry's cost.
• ENTRY_INFORMATION1..30 — The element's input values; these hold the actual pay amounts, hours, or rates feeding payroll calculations.
• DATE_EARNED, SOURCE_* columns — Support retroactive and period-specific processing by recording the earned date and the source run, period, and link.
• ATTRIBUTE1..20 — Standard descriptive flexfield (DFF) attribute columns.
• LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE — Standard WHO audit columns present on all Oracle HRMS/Payroll entities.

Common Use Cases and Queries

Typical uses include verifying currently active element entries for an assignment, feeding payroll reconciliation reports, and driving concurrent programs that must act only on effective-dated entries. A representative query:

SELECT pee.element_entry_id,
       pee.assignment_id,
       pee.element_link_id,
       pee.entry_type,
       pee.entry_information1,
       pee.effective_start_date,
       pee.effective_end_date
  FROM apps.pay_element_entries_x pee
 WHERE pee.assignment_id = :p_assignment_id
 ORDER BY pee.element_link_id;

Because the view already restricts to SYSDATE-effective rows, no additional date predicate is required for "as of today" logic. When historical or future-dated analysis is needed, query PAY_ELEMENT_ENTRIES_F directly and supply explicit EFFECTIVE_START_DATE/EFFECTIVE_END_DATE bounds. Queries against the _X view are read-only; inserts and updates must be performed against the base table or through the supported Payroll APIs.