Search Results pay_balance_validation




Overview

PAY_BALANCE_VALIDATION is a Payroll (PAY) module table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to hold "Balance Validity information," meaning it records the validation state and load history of defined payroll balances. In the EBS data model, balance validity governs whether a balance is considered active, current, and safe to use for payroll processing, costing, and reporting. Each row ties a defined balance to a business group and stamps the date on which that balance's data was loaded.

The ETRM metadata provides a heuristic Data Vault classification of standalone for this table. Read as a modeling suggestion, this implies the object is not a classic transactional hub or link, but behaves more like a reference/status satellite that captures the validity attributes of a defined balance at a point in time. The table carries only five documented columns, so it functions as a narrow supporting structure rather than a fact table.

Key Information Stored

The table is small by design, with five documented columns defining its entire physical shape.

  • BALANCE_VALIDATION_ID — the surrogate primary key, enforced by the PAY_BALANCE_VALIDATION_PK constraint. This is the system-generated identifier for each validity record.
  • DEFINED_BALANCE_ID — the business-key column pointing to the defined balance whose validity is being recorded. This is the first column of the PAY_BALANCE_VALIDATION_UK1 unique index.
  • BUSINESS_GROUP_ID — the business group partition key, the second column of PAY_BALANCE_VALIDATION_UK1. Together with DEFINED_BALANCE_ID, it guarantees only one validity record per defined balance within a business group.
  • RUN_BALANCE_STATUS — the status flag describing the run/validity state of the balance (for example, whether the balance has been run, is current, or requires recalculation).
  • BALANCE_LOAD_DATE — the timestamp marking when the balance validity record was loaded or refreshed.

The distinction between the surrogate key (BALANCE_VALIDATION_ID) and the business-key candidate (DEFINED_BALANCE_ID, BUSINESS_GROUP_ID) is important: integration and ETL logic should resolve to the unique index rather than the surrogate identifier when merging or validating data across business groups.

Common Use Cases and Queries

The primary use case is auditing which balances have been initialized or refreshed and when. A typical query joins the table to its defining balance to list current validity state by business group:

  • SELECT v.DEFINED_BALANCE_ID, v.BUSINESS_GROUP_ID, v.RUN_BALANCE_STATUS, v.BALANCE_LOAD_DATE FROM HR.PAY_BALANCE_VALIDATION v WHERE v.BUSINESS_GROUP_ID = :bg_id;
  • Identifying stale balances: SELECT DEFINED_BALANCE_ID FROM HR.PAY_BALANCE_VALIDATION WHERE BALANCE_LOAD_DATE < :cutoff_date;
  • Validating run status: SELECT RUN_BALANCE_STATUS, COUNT(*) FROM HR.PAY_BALANCE_VALIDATION GROUP BY RUN_BALANCE_STATUS;

Reporting consumers include payroll reconciliation dashboards, balance-load monitoring, and pre-run validation checks that confirm required balances are present and current before a payroll run is submitted.

Related Objects

Because the heuristic classification is standalone, there are no documented foreign-key parents or children. The most significant related objects are those implied by the documented columns and indexes:

  • PAY_DEFINED_BALANCES — parent of DEFINED_BALANCE_ID; supplies the balance definition referenced by each validity record.
  • PAY_BALANCE_VALIDATION_PK — primary-key index on BALANCE_VALIDATION_ID.
  • PAY_BALANCE_VALIDATION_UK1 — unique index on (DEFINED_BALANCE_ID, BUSINESS_GROUP_ID), the business-key enforcement.
  • HR_ORGANIZATION_UNITS / HR_ALL_ORGANIZATION_UNITS — resolve BUSINESS_GROUP_ID to the business group name.
  • PAY_BALANCE_TYPES / PAY_BALANCES — related balance metadata used in conjunction with validity state during payroll processing.
  • PAY_RUN_BALANCES — runtime balance results, compared against validity status to detect inconsistencies.