Search Results payfv_element_entries




Overview
Explore in AI Chat

Overview

The view APPS.PAYFV_ELEMENT_ENTRIES presents a denormalized, security-aware picture of payroll element entries captured against employee assignments within Oracle E-Business Suite Payroll (PAY). It consolidates data from element entry headers, element entry values, input values, element types and links, assignment and person records, and organization hierarchies, and it enriches the result with descriptive names resolved through the PAY_PAYFV_ELEMENT_ENTRIES_PKG package and standard Oracle lookup decoding. The view carries a VALID status in both the 12.1.1 and 12.2.2 releases and is owned by the APPS schema. Because it exposes meaningful, human-readable attributes — person name, element name, input value, entry value, and the assignment attributes (job, position, grade, location, pay basis, payroll) — it is intended for reporting and integration rather than for transactional maintenance. The "FV" prefix convention in Oracle Payroll indicates a "fast formula"/reporting-oriented view whose primary consumers are BI Publisher reports, custom SQL extracts, and downstream interfaces that need element entry detail without reconstructing the multi-table join themselves.

Underlying Base Objects

The view is defined over a wide join of Payroll and Human Resources core objects, all referenced through APPS synonyms except for the PER views. The Payroll objects are PAY_ELEMENT_ENTRIES_F (the element entry header), PAY_ELEMENT_ENTRY_VALUES_F (the per-input-value entry values), PAY_INPUT_VALUES_F and PAY_INPUT_VALUES_F_TL (input value definition and its translated name), PAY_ELEMENT_LINKS_F, PAY_ELEMENT_TYPES_F, and PAY_ELEMENT_TYPES_F_TL (element type and translated element name). The Human Resources objects are the PER_ASSIGNMENTS_F and PER_PEOPLE_F views and the HR_ALL_ORGANIZATION_UNITS_TL synonym, which is joined twice — once to resolve the assignment organization name and once to resolve the business group name. The view also references FND_USER twice to resolve the created-by and updated-by user names, and it depends on the PAY_PAYFV_ELEMENT_ENTRIES_PKG package to derive job, position, grade, location, pay basis, and payroll names. The HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages are referenced as part of the descriptive and security logic.

Key Columns

Common Use Cases and Queries

The view is typically used to report element entry values per assignment without writing the full multi-table join. A common query retrieves entries for a person and element alongside the input value and entered amount:

  • Element entry detail: SELECT person_name, element, input_value, entry_value, effective_start_date, effective_end_date FROM apps.payfv_element_entries WHERE person_name = :p_person AND element = :p_element ORDER BY effective_start_date;
  • Input value lookup: SELECT assignment_id, element, input_value, unit_of_measure, entry_value FROM apps.payfv_element_entries WHERE input_value = 'Amount';
  • Assignment context report: SELECT payroll_name, organization_name, job_name, grade_name, element, input_value, entry_value FROM apps.payfv_element_entries WHERE business_group_name = :p_bg;

Because the view is date-tracked through the underlying _F tables, queries should filter on effective dates where point-in-time results are required, and the ELEMENT_ENTRY_ID and ELEMENT_ENTRY_VALUE_ID columns should be used to trace results back to their source records.