Search Results payfv_balance_values




Overview
Explore in AI Chat

Overview

PAYFV_BALANCE_VALUES is a read-only database view owned by the APPS schema in Oracle E-Business Suite, registered as a VALID object within the PAY (Payroll) product module. Per the ETRM documentation, its stated description is simply "copy of the view pay_balance_values_v," indicating that it is a functional duplicate of the core balance values view rather than an independent object with unique logic. It exposes payroll balance value records — the accumulated or processed results of balance definitions — for consumption by reporting tools, integrations, and downstream extracts. Because payroll balances drive calculations such as gross-to-net, deductions, and year-to-date accumulations, this view serves as a convenient publication point for balance data outside of the internal payroll calculation engine.

Underlying Base Objects

The view text selects directly from PAY_BALANCE_VALUES_V, projecting all eighteen of that underlying view's columns without transformation, joins, or filters. The documented referenced base objects are FND_DATE (PACKAGE), PAY_BALANCE_PKG (PACKAGE), and PAY_BALANCE_VALUES_V (VIEW). FND_DATE is the standard Oracle Application Object Library package used for date conversion and formatting, while PAY_BALANCE_PKG encapsulates the balance processing logic used within the payroll run. PAY_BALANCE_VALUES_V is therefore the immediate parent view, and PAYFV_BALANCE_VALUES can be understood as a naming-convention alias intended to satisfy a specific interface or compatibility requirement — commonly a legacy or third-party naming standard that expects the "PAYFV" prefix. All data returned originates from PAY_BALANCE_VALUES_V and, transitively, from the underlying PAY balance tables maintained by PAY_BALANCE_PKG.

Key Columns

The view exposes the following columns, each consistent with the base balance structure:

  • ASSIGNMENT_ACTION_ID — Identifier of the payroll action applied to the assignment; links to the assignment action that produced the balance value.
  • ASSIGNMENT_ID — The employee or applicant assignment to which the balance belongs.
  • PAYROLL_ACTION_ID / PAYROLL_ID — The payroll action and payroll that generated the record, enabling linkage to payroll run results.
  • EFFECTIVE_DATE — The date on which the balance value is effective; critical for date-effective and retroactive reporting.
  • BALANCE_TYPE_ID / BALANCE_NAME — The balance definition identifier and its user-facing name (for example, a specific gross or deduction balance).
  • BALANCE_DIMENSION_ID / DIMENSION_NAME / DIMENSION_DESCRIPTION / DATABASE_ITEM_SUFFIX — Dimensional context of the balance, identifying the dimension and the database item that stores the value.
  • DEFINED_BALANCE_ID — The defined balance instance associated with the value.
  • ROUTE_ID — Routing identifier for the balance value record.
  • VALUE — The numeric balance amount itself, the primary measure of interest.
  • TAX_GROUP / JURISDICTION — Tax grouping and jurisdiction context, relevant for statutory and localization reporting.
  • SOURCE_ID — Identifier of the source record that produced the value.
  • BUSINESS_GROUP_ID — The enterprise business group, enforcing multi-tenant data separation.

Common Use Cases and Queries

Typical scenarios include extracting balance values for a payroll run, auditing a specific assignment's balance history, and feeding balance data into external payroll analytics or data warehouses. Because the view is a direct projection of PAY_BALANCE_VALUES_V, query patterns mirror those used against the parent view. A representative query retrieving balance values for a given assignment and effective period is shown below:

  • Balance by assignment: SELECT assignment_id, balance_name, effective_date, value FROM payfv_balance_values WHERE assignment_id = :p_assignment_id AND effective_date BETWEEN :p_start AND :p_end ORDER BY effective_date;
  • Balance by payroll run: SELECT payroll_id, balance_name, SUM(value) FROM payfv_balance_values WHERE payroll_id = :p_payroll_id GROUP BY payroll_id, balance_name;
  • Dimension-level detail: SELECT dimension_name, tax_group, jurisdiction, value FROM payfv_balance_values WHERE business_group_id = :p_bg_id AND balance_type_id = :p_balance_type_id;

Queries should always constrain on BUSINESS_GROUP_ID where multi-organization data is present, and on EFFECTIVE_DATE to bound retroactive or cumulative records. Because the view performs no aggregation itself, totals must be computed by the calling SQL. Access is subject to standard APPS schema grants and any custom synonyms or security profiles configured at the site.