Search Results pay_balance_categories_f




Overview
Explore in AI Chat

Overview

PAY_BALANCE_CATEGORIES_F is a core Payroll (PAY) reference table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. As its description states, it holds seeded categories for balances, providing the classification framework that organizes payroll balance definitions into logical groupings such as Earnings, Deductions, Tax, and Employer Contributions. Each category acts as the highest-level tag applied to a balance, enabling payroll processes, reports, and statutory extracts to select balances by category rather than by individual balance name.

The table is date-effective (the "_F" suffix denotes a date-tracked, non-translated entity), and is delivered as seeded, Oracle-maintained reference data. Rows carry EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, so historical and future-dated versions of a category coexist without overwriting prior definitions. The table is not translation-enabled; the USER_CATEGORY_NAME column allows a customer-defined display label distinct from the seeded CATEGORY_NAME.

The ETRM heuristic Data Vault classification for this object is standalone, meaning it is modeled as a reference or hub-style entity without a mined dependency on a parent link structure. In practice the table behaves as a reference hub that downstream balance-definition and balance-value satellites resolve against.

Key Information Stored

The most significant columns include:

  • BALANCE_CATEGORY_ID — surrogate primary key component, uniquely identifying each category record in combination with the effective dates.
  • CATEGORY_NAME — the seeded category name; part of the business-key unique index.
  • LEGISLATION_CODE — indicates the legislation (country) under which the category is valid; also part of the unique index.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-effective boundaries that govern which version of a category applies at any point in time.
  • SAVE_RUN_BALANCE_ENABLED — controls whether balances in this category are persisted when a payroll run is saved, directly influencing payroll performance and auditability.
  • USER_CATEGORY_NAME — customer-facing label overriding the seeded name.
  • PBC_INFORMATION_CATEGORY and PBC_INFORMATION1–30 — descriptive flexfield context and attribute segments, available for extending the seeded category with site-specific information.
  • BUSINESS_GROUP_ID — the owning business group, aligning the row to a specific enterprise configuration.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — the standard Oracle EBS WHO columns and optimistic locking column.
  • ZD_EDITION_NAME — a 12.2.x editioning/online-patching column; note it also appears in the unique index.

The surrogate primary key is PAY_BALANCE_CATEGORIES_F_PK (BALANCE_CATEGORY_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE). The secondary unique index, PAY_BALANCE_CATEGORIES_F_UK (CATEGORY_NAME, LEGISLATION_CODE, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, ZD_EDITION_NAME), is the business-key candidate that guarantees a category name is unique within a legislation for a given effective period.

Common Use Cases and Queries

Functional consultants and developers query this table when building payroll reports that group balances by category, when diagnosing missing or misclassified balances after a legislation patch, and when reviewing SAVE_RUN_BALANCE_ENABLED settings that affect run performance.

A typical current-row query:

  • SELECT balance_category_id, category_name, user_category_name, legislation_code FROM pay_balance_categories_f WHERE legislation_code = 'US' AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;

Joins from balance definitions to their category are common in earnings/deduction reporting, conversion of balance-category extracts to legislative reporting, and validation of fast formulas that filter by category. Because the table is date-effective, all reporting SQL should filter on the effective date window rather than assuming a single row per category. The PBC flexfield columns are typically surfaced through the descriptive flexfield in the Payroll setup forms rather than queried directly, but they can be extracted for interface feeds where a customer has stored routing or integration metadata in the segment attributes.

Related Objects

The following objects are most commonly associated with PAY_BALANCE_CATEGORIES_F through shared keys and Payroll reference flows:

These relationships make PAY_BALANCE_CATEGORIES_F a foundational reference for balance definition, payroll run persistence, and statutory balance reporting across Oracle EBS 12.1.1 and 12.2.2.