Search Results pay_element_entries_v




Overview
Explore in AI Chat

Overview

PAY_ELEMENT_ENTRIES_V is an APPS-owned view in the Oracle E-Business Suite Payroll (PAY) module, documented in ETRM 12.2.2 and present in both 12.1.1 and 12.2.2 environments. Its documented purpose is to support the user interface rather than to serve as a standalone reporting entity, and its structure reflects that design intent: it consolidates a set of denormalized, display-oriented attributes drawn from the element entry, element link, input value, and element type configuration tables.

The view is of particular interest to implementers searching on the term "entry_value" because it exposes the resolved ENTRY_VALUE column alongside the raw SCREEN_ENTRY_VALUE. The former is produced by applying the HR_CHKFMT.CHANGEFORMAT function to the stored screen entry value, converting it according to the unit of measure (INV.UOM) and the element's output currency code. This means the view performs on-the-fly formatting logic that does not exist in the underlying PAY_ELEMENT_ENTRY_VALUES_F table.

Underlying Base Objects

The view is defined over eight documented base objects, all accessed through APPS synonyms:

  • PAY_ELEMENT_ENTRIES_F — the element entry header, filtered to ENTRY_TYPE = 'B' (both entries)
  • PAY_ELEMENT_ENTRY_VALUES_F — the individual input value rows for each entry
  • PAY_ELEMENT_LINKS_F — the element link that ties the element to the assignment
  • PAY_ELEMENT_TYPES_F — the element definition, supplying the output currency code
  • PAY_ELEMENT_TYPES_F_TL — the translated element name, restricted to USERENV('LANG')
  • PAY_INPUT_VALUES_F — the input value definition and unit of measure
  • PAY_INPUT_VALUES_F_TL — the translated input value name, also language-restricted
  • HR_CHKFMT (PACKAGE) — the formatting routine applied to produce ENTRY_VALUE

All joins are date-effective. Each of the entry, entry value, element type, and element link joins carries a BETWEEN ... EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE predicate anchored on PEE.EFFECTIVE_START_DATE, which is the datetracked date of the element entry. This is the defining characteristic of the view: it returns the version of each configuration object that was in force on the entry's effective date, not simply the current row.

Key Columns

  • ELEMENT_NAME — the translated name of the element, from PAY_ELEMENT_TYPES_F_TL.
  • NAME — the translated name of the input value to which the entry value belongs.
  • ENTRY_VALUE — the formatted, user-facing value produced by HR_CHKFMT.CHANGEFORMAT, applying the UOM and currency.
  • SCREEN_ENTRY_VALUE — the raw stored value as captured on the entry screen.
  • ELEMENT_ENTRY_ID — the primary key of the underlying element entry row.
  • ASSIGNMENT_ID and ASSIGNMENT_ACTION_ID — note that ASSIGNMENT_ACTION_ID is aliased from PEE.CREATOR_ID, a legacy naming artifact.
  • DISPLAY_SEQUENCE — ordering attribute for presenting input values.
  • The four *_EFFECTIVE_START_DATE / *_EFFECTIVE_END_DATE pairs (INV_, PEV_, PEE_) expose the datetracked ranges of the input value definition, the entry value, and the entry itself.

Common Use Cases and Queries

Typical usage is diagnostic or interface-oriented: confirming how a value will be rendered to a user, extracting entries for a specific assignment, or reconciling stored values against their formatted equivalents. Because the view performs formatting and language filtering, it is unsuitable for bulk payroll calculations; use the base tables for those.

A representative query retrieving formatted values for an assignment is:

  • SELECT element_name, name, entry_value, screen_entry_value, display_sequence
  • FROM apps.pay_element_entries_v
  • WHERE assignment_id = :p_assignment_id
  • ORDER BY element_name, display_sequence;

To identify discrepancies between stored and formatted values, compare SCREEN_ENTRY_VALUE against ENTRY_VALUE for a given ELEMENT_ENTRY_ID. Note that USERENV('LANG') governs returned translations, so results vary by session language.