Search Results pay_ranges_f_pk

Overview

The PAY_RANGES_F table, owned by the HR schema, is a foundational data object within the Oracle EBS Payroll (PAY) module. It stores the discrete range or band definitions that belong to each tax table number recorded in PAY_RANGE_TABLES_F. In payroll tax processing, governments and tax authorities commonly publish graduated tables in which rates, thresholds, or flat amounts vary by income band, contribution ceiling, or filing status. PAY_RANGES_F holds precisely those bands, capturing the low and high boundaries together with the associated calculation amounts. It is therefore a configuration and reference table that drives payroll tax calculation, deduction processing, and range-based validation during payroll runs.

From a Data Vault modeling perspective, the metadata's heuristic classification is standalone — that is, no foreign-key relationships were mined from the documented schema. This should be treated as a modeling suggestion only: the object functions effectively as a reference or lookup satellite, carrying descriptive attributes (band boundaries and amounts) tied to a parent range table identified by RANGE_TABLE_ID, while the absence of a mined FK reflects the fact that the association is maintained implicitly rather than through a declared database constraint.

Key Information Stored

Each row in PAY_RANGES_F represents a single range within a parent tax table. The most significant columns are:

• RANGE_ID — the surrogate primary key, defined by the PAY_RANGES_F_PK constraint, uniquely identifying each range row.
• RANGE_TABLE_ID — the parent reference linking the range to a tax table number in PAY_RANGE_TABLES_F. This column participates in the PAY_RANGE_F_UK1 unique index and is the principal business-key candidate.
• LOW_BAND and HIGH_BAND — the lower and upper boundaries of the range, defining the income or amount interval to which the row applies.
• AMOUNT1 through AMOUNT8 — a series of up to eight calculation or rate amounts associated with the band. These values support the arithmetic applied when payroll determines the tax or deduction for a given employee's taxable base falling within the range.
• EFFECTIVE_START_DATE and EFFECTIVE_END_DATE — date-effective columns that provide the temporal validity of each range, supporting legislative updates and rate changes over time. They also form part of the PAY_RANGE_F_UK1 unique index, ensuring no overlapping or duplicate bands per table and effective period.
• OBJECT_VERSION_NUMBER — the standard EBS optimistic-locking column, used to detect concurrent updates.

The documented schema contains fifteen columns in total; the remainder are additional amount or attribute fields of secondary importance to most reporting scenarios.

Common Use Cases and Queries

Typical usage centers on retrieving the correct band for a given taxable amount and effective date, and on reporting the parameterization of tax tables. A common pattern joins the range table to its parent for a readable list of bands:

• Validation queries to confirm that bands are contiguous and non-overlapping for a given RANGE_TABLE_ID, which is essential when auditing tax table setup.
• Point-in-time queries filtering on EFFECTIVE_START_DATE and EFFECTIVE_END_DATE to obtain the range in force for a particular payroll period.
• Band resolution logic that selects the row where the employee's taxable base lies between LOW_BAND and HIGH_BAND, then applies the corresponding AMOUNT1…AMOUNT8 values.
• Reporting on tax table changes over time by comparing effective-dated versions of the same RANGE_TABLE_ID.

A representative query takes the form: SELECT range_id, low_band, high_band, amount1 FROM pay_ranges_f WHERE range_table_id = :p_table_id AND :p_effective_date BETWEEN effective_start_date AND effective_end_date ORDER BY low_band;

Related Objects

The following objects are most significant in relation to PAY_RANGES_F:

• PAY_RANGE_TABLES_F — the parent table holding each Tax Table Number; joined on PAY_RANGES_F.RANGE_TABLE_ID = PAY_RANGE_TABLES_F.RANGE_TABLE_ID. This is the primary relationship in the range model.
• PAY_RANGE_TABLES_F (effective-dated rows) — the date-effective counterpart providing table-level validity consistent with the range rows.
• PAY_RUN_RESULTS_F / payroll run result tables — indirectly dependent, as calculated tax and deduction values are produced using the ranges resolved from this table.
• PAY_ELEMENT_TYPES_F — element definitions that reference tax tables and therefore consume the range data during payroll processing.
• PAY_BALANCES — balance definitions against which banded calculations may be applied.

Because the metadata records no mined foreign keys, these associations should be treated as logical relationships validated in application code and configuration rather than enforced database constraints.