Search Results per_bf_balance_amounts




Overview
Explore in AI Chat

Overview

The PER_BF_BALANCE_AMOUNTS table is a core transactional data store within the Oracle E-Business Suite Human Resources (HR) module, specifically for releases 12.1.1 and 12.2.2. Its primary role is to capture and persist detailed balance amounts generated during the "backfeed" process from Oracle Payroll to Oracle Human Resources. This backfeed mechanism is critical for ensuring that payroll calculations, such as earnings and deductions, are accurately reflected in HR for subsequent reporting, benefits administration, and compliance tracking. The table operates at the assignment level and organizes data by payroll processing period, serving as the definitive repository for summarized payroll balance values that are fed back into the HR system.

Key Information Stored

The table stores assignment-level balance summaries linked to specific payroll processing runs. Key columns include the primary key BALANCE_AMOUNT_ID, which uniquely identifies each record. The PROCESSED_ASSIGNMENT_ID column links to the PER_BF_PROCESSED_ASSIGNMENTS table, identifying the specific assignment and payroll run instance. The BALANCE_TYPE_ID is a foreign key to PER_BF_BALANCE_TYPES, defining the category of balance (e.g., a specific type of taxable gross or deduction total). The BUSINESS_GROUP_ID, a foreign key to HR_ALL_ORGANIZATION_UNITS, secures data by the appropriate organizational tenant. Crucially, the table holds the calculated RUN_AMOUNT_VALUE and SUMMARY_VALUE for the specified balance type over the processing period, providing both the detailed run result and any cumulative summary.

Common Use Cases and Queries

A primary use case is auditing and reconciling payroll data within HR. Analysts query this table to verify that backfeed totals match expected payroll run results. Another common scenario is generating custom reports on employee compensation history or deduction accumulations for benefits eligibility, which rely on the summarized balance values. A typical query pattern involves joining to related assignment and balance type tables to produce readable reports.

Sample SQL Pattern:

  • SELECT ppa.assignment_number, pbt.balance_name, pba.run_amount_value, pba.summary_value
  • FROM per_bf_balance_amounts pba,
  • per_bf_processed_assignments ppa,
  • per_bf_balance_types pbt
  • WHERE pba.processed_assignment_id = ppa.processed_assignment_id
  • AND pba.balance_type_id = pbt.balance_type_id
  • AND ppa.payroll_id = :p_payroll_id
  • AND ppa.period_end_date = :p_period_end;

Related Objects

The PER_BF_BALANCE_AMOUNTS table is centrally connected to several key objects via documented foreign key relationships, forming the core of the payroll backfeed data model.

  • PER_BF_PROCESSED_ASSIGNMENTS: Joined via PROCESSED_ASSIGNMENT_ID. This is the primary parent table, providing context for the specific assignment and payroll period for which the balance was calculated.
  • PER_BF_BALANCE_TYPES: Joined via BALANCE_TYPE_ID. This relationship defines the semantic meaning of the stored amount, such as "Regular Earnings" or "401(k) Deferral YTD."
  • HR_ALL_ORGANIZATION_UNITS: Joined via BUSINESS_GROUP_ID. This enforces data security at the business group level, a fundamental multi-org structure in Oracle HRMS.