Search Results processing_date




Overview

The PER_BF_BALANCES_V view is a reporting object owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PER (Human Resources) product family. Its name reflects its association with the Balance Feed ("BF") data model used by Oracle Payroll and HRMS to store, aggregate, and report balance results derived from payroll processing. The view consolidates balance amounts calculated for processed assignments together with the descriptive attributes of each balance type and the identifying attributes of the payroll run that produced them. Because it exposes payroll run context — including period start date, period end date, and PROCESSING_DATE — it is particularly useful for time-based reporting, period-over-period comparison, and reconciliation of payroll results. In Oracle EBS 12.1.1 and 12.2.2 the object remains a read-only, valid view intended for query and reporting rather than direct DML.

Underlying Base Objects

According to the documented metadata, the view is defined over four synonym-backed base objects: PER_BF_BALANCE_AMOUNTS, PER_BF_BALANCE_TYPES, PER_BF_PAYROLL_RUNS, and PER_BF_PROCESSED_ASSIGNMENTS. The view text joins these on their primary keys: BV.BALANCE_TYPE_ID = BT.BALANCE_TYPE_ID, BV.PROCESSED_ASSIGNMENT_ID = PA.PROCESSED_ASSIGNMENT_ID, and PA.PAYROLL_RUN_ID = PYR.PAYROLL_RUN_ID. The balance amount row (BV) supplies the aggregated monetary or unit values; the balance type (BT) supplies descriptive metadata such as name, unit of measure, and category; the processed assignment (PA) links each balance to the assignment it was calculated for; and the payroll run (PYR) provides the run, payroll, and date context.

Key Columns

  • BALANCE_VALUE_ID / BALANCE_TYPE_ID — Identifiers for the balance value row and the balance type being reported.
  • PROCESSED_ASSIGNMENT_ID / ASSIGNMENT_ID — The processed assignment record and the underlying assignment to which the balance belongs.
  • PAYROLL_RUN_ID / PAYROLL_ID / PAYROLL_IDENTIFIER — The payroll run and payroll that generated the balance.
  • BUSINESS_GROUP_ID — The HR business group owning the data, essential for multi-organization filtering.
  • BALANCE_NAME / UOM / CATEGORY — Descriptive attributes of the balance type (displayed name, unit of measure, and category).
  • YTD_AMOUNT, FYTD_AMOUNT, PTD_AMOUNT, MTD_AMOUNT, QTD_AMOUNT, RUN_AMOUNT — Aggregated balance values for year-to-date, fiscal year-to-date, period-to-date, month-to-date, quarter-to-date, and run-to-date respectively.
  • PERIOD_START_DATE / PERIOD_END_DATE — The payroll period boundaries for the run.
  • PROCESSING_DATE — The date on which the payroll run was processed, the column most commonly used for time-based filtering and reporting.

Common Use Cases and Queries

This view is typically queried for payroll balance reporting, audit, and integration extracts. A frequent pattern filters by business group and a date range on PROCESSING_DATE, for example:

  • Period reporting: SELECT assignment_id, balance_name, ptd_amount, processing_date FROM per_bf_balances_v WHERE business_group_id = :bg AND processing_date BETWEEN :from_date AND :to_date ORDER BY processing_date;
  • Run-level reconciliation: grouping by payroll_identifier and processing_date to sum run_amount per run.
  • Year-to-date extracts: selecting ytd_amount by assignment and balance name for downstream interfaces.

Because the view is read-only, all access should be through SELECT statements, respecting business group and date filters to maintain performance.