Search Results balance_value_id

Overview

APPS.PER_BF_BALANCES_V is a supplementary database view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments. It is owned by the APPS schema and registered under FND Design Data as PER.PER_BF_BALANCES_V, with a current status of VALID. The view is classified as a "supplementary view used to simplify forms coding," which indicates that it was created primarily to support Oracle Forms-based user interfaces within the Oracle Payroll and HRMS modules rather than as a general-purpose reporting object.

Oracle explicitly warns that it does not recommend querying or altering data using this view, as its definition may change dramatically in subsequent minor or major releases. This is an important consideration for developers and support personnel: while the view remains usable for read-only queries, dependency on it in custom code carries maintenance risk across upgrades and patches.

The view presents payroll balance information, combining balance amounts across multiple time dimensions (year-to-date, fiscal year-to-date, period-to-date, month-to-date, quarter-to-date, and run amounts) alongside descriptive attributes such as balance name, unit of measure, and category. This makes it structurally appealing for balance reporting, though its intended use remains form-driven.

Underlying Base Objects

The view is defined over four documented base objects, each referenced as a synonym within APPS:

• PER_BF_BALANCE_AMOUNTS — supplies the numeric balance values across YTD, FYTD, PTD, MTD, QTD, and RUN dimensions.
• PER_BF_BALANCE_TYPES — defines the balance definitions, including name, UOM, and category.
• PER_BF_PAYROLL_RUNS — provides payroll run context such as run identifier, payroll identifier, and period dates.
• PER_BF_PROCESSED_ASSIGNMENTS — links the balance data to processed assignment and assignment identifiers.

The view is additionally exposed through a PUBLIC synonym PER_BF_BALANCES_V, allowing referencing outside the APPS schema subject to grants. No other database objects are documented as referencing it, reinforcing its role as a terminal presentation layer for forms.

Key Columns

The BALANCE_VALUE_ID column, which is the term most frequently searched by users, is the primary key that uniquely identifies each balance value record returned by the view. It is a NUMBER column and serves as the natural join point for retrieving a specific balance entry.

Other key columns include:

• BALANCE_TYPE_ID — foreign key to the balance type definition governing name, UOM, and category.
• ASSIGNMENT_ID and PROCESSED_ASSIGNMENT_ID — identify the employee assignment associated with the balance.
• PAYROLL_ID and PAYROLL_RUN_ID — identify the payroll and specific run that produced the balances.
• BUSINESS_GROUP_ID — business group context, length 15.
• BALANCE_NAME, UOM, CATEGORY — descriptive attributes sourced from the balance type.
• YTD_AMOUNT, FYTD_AMOUNT, PTD_AMOUNT, MTD_AMOUNT, QTD_AMOUNT, RUN_AMOUNT — the accumulated balance amounts across each time dimension.
• PERIOD_START_DATE, PERIOD_END_DATE, PROCESSING_DATE — the period and processing timestamps.

Common Use Cases and Queries

Typical scenarios involve reconciling payroll balances for a given assignment or payroll run, verifying accumulated YTD and PTD amounts, and supporting payroll auditing or extract processes. Because the view joins balance amounts to assignment and run context, it is convenient for drill-down from a run to individual employee balances.

For example, to retrieve balances for a specific assignment:

SELECT balance_value_id, balance_name, uom,
       ytd_amount, ptd_amount, run_amount,
       period_start_date, period_end_date
FROM   apps.per_bf_balances_v
WHERE  assignment_id = :p_assignment_id
ORDER BY period_end_date DESC;

To find a specific balance record by its identifier:

SELECT * FROM apps.per_bf_balances_v
WHERE balance_value_id = :p_balance_value_id;

Given the documented warning regarding potential structural changes across releases, any custom development should isolate references to this view behind a wrapper or, where feasible, query the underlying base tables directly. This preserves upgrade resilience while still leveraging the convenient shape of PER_BF_BALANCES_V for forms-oriented processing.