Search Results dimension_description




Overview

APPS.PAYFV_BALANCE_VALUES is a reporting and integration view in Oracle E-Business Suite (documented for 12.1.1 and 12.2.2) that exposes payroll balance values for assignments, payroll actions, and defined balances. It presents a flattened projection of payroll balance data by selecting from PAY_BALANCE_VALUES_V, the underlying balance values view. The "F" designation in the name indicates a flexfield-oriented or functionally derived view commonly used in Oracle HRMS/Payroll reporting layers.

The view surfaces one row per balance value entry, keyed by ASSIGNMENT_ACTION_ID, ASSIGNMENT_ID, and DEFINED_BALANCE_ID. This makes it suitable for downstream reporting, ad hoc SQL, and integration extracts that require payroll balance results rather than raw payroll run detail. The presence of DIMENSION_DESCRIPTION and DIMENSION_NAME directly supports the user's search context: it allows consumers to categorize and filter balances by dimensional context (for example, assignment-level, tax-group-level, or jurisdiction-level dimensions) without needing to join to separate dimension metadata.

Underlying Base Objects

The view is defined over PAY_BALANCE_VALUES_V, which itself resolves against core payroll balance objects. Documented referenced base objects include:

  • PAY_BALANCE_VALUES_V — the immediate source view from which all columns are selected.
  • PAY_BALANCE_PKG — the payroll balances package that supplies the business logic, value derivation, and balance resolution used in the underlying chain.
  • FND_DATE — the Applications date-handling package used for effective date formatting and conversion.

Because PAYFV_BALANCE_VALUES is a pass-through projection of PAY_BALANCE_VALUES_V, its cost and behavior are governed by the performance of that underlying view and its dependencies. It does not introduce additional joins or predicates of its own.

Key Columns

  • ASSIGNMENT_ACTION_ID / ASSIGNMENT_ID — identity of the assignment action and assignment to which the balance belongs.
  • PAYROLL_ACTION_ID / PAYROLL_ID — the payroll action and payroll context for the balance.
  • EFFECTIVE_DATE — the date on which the balance value applies.
  • BALANCE_TYPE_ID / BALANCE_NAME — identifier and human-readable name of the balance being reported.
  • BALANCE_DIMENSION_ID / DIMENSION_NAME / DIMENSION_DESCRIPTION — the dimension context, including the description commonly used for labeling and grouping in reports.
  • DATABASE_ITEM_SUFFIX — the suffix used to map the balance to its database item.
  • DEFINED_BALANCE_ID — the defined balance that produced the row.
  • ROUTE_ID / SOURCE_ID — routing and originating source identifiers.
  • VALUE — the numeric balance value.
  • TAX_GROUP / JURISDICTION — tax reporting context.
  • BUSINESS_GROUP_ID — the HR business group for multi-organization filtering.

Common Use Cases and Queries

The view is typically used to extract balance values by assignment, payroll period, and balance name, often filtered by business group and dimension for reporting accuracy.

SELECT assignment_id,
       balance_name,
       dimension_name,
       dimension_description,
       effective_date,
       value
  FROM apps.payfv_balance_values
 WHERE business_group_id = :p_bg_id
   AND assignment_id = :p_assignment_id
   AND effective_date BETWEEN :p_start AND :p_end;

For reporting on balance values grouped by dimension:

SELECT dimension_name,
       dimension_description,
       SUM(value) total_value
  FROM apps.payfv_balance_values
 WHERE payroll_id = :p_payroll_id
   AND business_group_id = :p_bg_id
 GROUP BY dimension_name, dimension_description;

Common scenarios include payroll balance extracts for payroll-to-GL reconciliation, tax reporting using TAX_GROUP and JURISDICTION, and integration feeds keyed by ASSIGNMENT_ACTION_ID. Because the view is unprotected (no row-level security logic of its own), callers should always filter by BUSINESS_GROUP_ID where appropriate to respect multi-organization boundaries.