Search Results pay_run_balances




Overview
Explore in AI Chat

Overview

The PAY_RUN_BALANCES table is a core data repository within the Oracle E-Business Suite Payroll module (PAY). It functions as the definitive store for run-level balances, which are temporary, calculated totals of earnings, deductions, taxes, and other payroll elements generated for a specific payroll processing run. These balances are not the final, cumulative balances for an employee but represent the incremental values for a single payroll period. The table's role is critical for the payroll calculation engine, enabling the accurate computation of taxes, benefits, and other dependent calculations within a run by providing access to intermediate results. It is a foundational object for payroll reporting and audit trails for any processed period.

Key Information Stored

The table's primary purpose is to link a specific calculated balance value to the payroll run and assignment that produced it. Its key columns, as indicated by its foreign key relationships, include RUN_BALANCE_ID (the primary key), ASSIGNMENT_ACTION_ID, PAYROLL_ACTION_ID, and DEFINED_BALANCE_ID. The ASSIGNMENT_ACTION_ID links the balance to a specific assignment action (i.e., the processing of a single employee's assignment within a run). The PAYROLL_ACTION_ID links to the overarching payroll action that defines the entire run. The DEFINED_BALANCE_ID is a foreign key to PAY_DEFINED_BALANCES, which identifies the specific balance type being stored (e.g., "Regular Earnings YTD," "Federal Taxable Gross"). The table also contains VALUE columns (though not explicitly listed in the provided metadata, they are standard) that hold the actual numerical balance amounts.

Common Use Cases and Queries

A primary use case is troubleshooting and auditing payroll run results. Analysts query this table to verify the calculated values for specific balances for an employee in a given period. Another critical use is for generating detailed payroll registers and reports that break down run-level contributions. A common query pattern involves joining to assignment, person, and balance definition tables. For example, to find the run-level regular earnings for an employee in a specific payroll run, one might use a SQL pattern similar to:

  • SELECT ppa.effective_date, ppf.full_name, pdb.balance_name, prb.value
  • FROM pay_run_balances prb,
  • pay_assignment_actions paa,
  • pay_payroll_actions ppa,
  • pay_defined_balances pdb,
  • per_all_people_f ppf
  • WHERE prb.assignment_action_id = paa.assignment_action_id
  • AND prb.payroll_action_id = ppa.payroll_action_id
  • AND prb.defined_balance_id = pdb.defined_balance_id
  • AND paa.assignment_id = ppf.assignment_id
  • AND ppa.payroll_action_id = :run_id
  • AND pdb.balance_name LIKE 'Regular Earnings%';

Related Objects

The PAY_RUN_BALANCES table is centrally connected to other key payroll tables via documented foreign keys. Its primary relationships are:

  • PAY_DEFINED_BALANCES: Joined via PAY_RUN_BALANCES.DEFINED_BALANCE_ID. This link provides the metadata describing the type of balance stored (e.g., its name, classification, and dimension).
  • PAY_ASSIGNMENT_ACTIONS: Joined via PAY_RUN_BALANCES.ASSIGNMENT_ACTION_ID. This links the balance to the specific instance of processing for an employee's assignment within a payroll run.
  • PAY_PAYROLL_ACTIONS: Joined via PAY_RUN_BALANCES.PAYROLL_ACTION_ID. This links the balance to the master record of the payroll run itself, which contains run-level effective dates and status.

These relationships are essential for traversing from a raw balance value to its contextual meaning (defined balance), the employee assignment it belongs to, and the payroll period it was calculated for.