Results for “pay_defined_balances_uk2”

22 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PAY_DEFINED_BALANCES, owned by the HR schema in Oracle EBS 12.1.1 and 12.2.2, is the intersection table between balance types and balance dimensions. Its purpose is to fully qualify a payroll balance: a balance type (for example, Gross Pay) combined with a balance dimension (for example, Year to Date) yields a specific defined balance. This defined balance is the entity referenced by name in Oracle Payroll FastFormula logic through its associated database item, effectively providing the runtime pointer that formulas use when retrieving accumulated values. The object status is VALID and its FND design data reference is PAY.PAY_DEFINED_BALANCES.

From a modeling perspective, the heuristic Data Vault classification of this table is a hub, derived from its foreign key structure. It carries a single-column surrogate primary key and acts as the durable business concept (the qualified balance definition) that other satellite-style transaction and accumulation tables point to.

Key Information Stored

The primary key is DEFINED_BALANCE_ID, a system-generated surrogate number enforced by the unique index PAY_DEFINED_BALANCES_PK. The business-key candidates are captured by the unique index PAY_DEFINED_BALANCES_UK2, which combines BALANCE_TYPE_ID, BALANCE_DIMENSION_ID, BUSINESS_GROUP_ID, and LEGISLATION_CODE (together with the edition column on 12.2.x). This composite uniqueness enforces that a given balance type/dimension pairing is valid only once per business group and legislation.

Common Use Cases and Queries

The table is central to payroll balance reporting, formula troubleshooting, and setup validation. Analysts typically join it to its parents to resolve the readable balance name and dimension meaning:

  • Resolving a defined balance ID returned by a formula or a run-balance row into text for reconciliation reports.
  • Enumerating the defined balances available to a specific business group and legislation before authoring FastFormula.
  • Auditing which balance/dimension combinations exist for a given balance type, using the UK2 business key.

A representative query resolves the described balance:

SELECT pdb.defined_balance_id, pbt.balance_name, pbd.dimension_name
FROM pay_defined_balances pdb, pay_balance_types pbt, pay_balance_dimensions pbd
WHERE pdb.balance_type_id = pbt.balance_type_id
AND pdb.balance_dimension_id = pbd.balance_dimension_id
AND pdb.business_group_id = :bg_id;

Related Objects

Dependency relationships confirm PAY_DEFINED_BALANCES as a hub referenced widely by balance-storage and rule tables (join on DEFINED_BALANCE_ID unless noted):