Search Results pay_range_tables_f_pk

Overview

PAY_RANGE_TABLES_F is the core definition table for Range Tables within the Oracle Payroll (PAY) module, owned by the HR schema. Range tables are user-defined grids that cross-reference two or more variables so that a value can be selected automatically based on the intersection of inputs. In the payroll and benefits context they are typically used to drive calculations such as tax withholding tables, wage bracket amounts, benefit rate lookups, and jurisdictional banding. Each row in PAY_RANGE_TABLES_F represents a single cell (value) within a range table, and the table's effective-dated structure allows an installation to maintain multiple historic and future versions of the same table for date-effective payroll processing.

The table is date-effective and includes the standard Oracle EBS "flexfield" columns, DESCRIPTIVE flexfield columns, and DDF columns. Mined from its foreign-key structure, the ETRM metadata classifies this object heuristically as a standalone Data Vault candidate. In Data Vault modeling terms a standalone classification most closely resembles a satellite object: it stores descriptive and value attributes (the cell value, period frequency, UOM, earnings type, and DFF content) keyed by its parent business key, RANGE_TABLE_ID. There is no separate hub or link strictly identified for this table, so the RANGE_TABLE_ID should be understood as the de facto business key that would be carried into a hub (or is inherited from a range-table header).

Key Information Stored

PAY_RANGE_TABLES_F contains 77 documented physical columns. The most consequential for reporting and integration are:

• RANGE_TABLE_ID — Surrogate identifier for the range table (or range table definition) that this cell belongs to. It participates directly in the primary key.
• EFFECTIVE_START_DATE and EFFECTIVE_END_DATE — The date-effectivity bounds. Together with RANGE_TABLE_ID they form the composite primary key PAY_RANGE_TABLES_F_PK and the unique index that establishes the business-key candidate.
• RANGE_TABLE_NUMBER — The numeric cell or bracket number within the table (e.g., the row/bracket indicator).
• ROW_VALUE_UOM — Unit of measure for the row value, used when the intersection coordinate has a scale (currency, percentage, hours, etc.).
• PERIOD_FREQUENCY — The payroll period frequency that the cell value applies to (weekly, biweekly, monthly, etc.).
• EARNINGS_TYPE — The earnings element to which the range-table value is tied, linking the cell to specific pay elements.
• BUSINESS_GROUP_ID — Multi-tenant / legislative grouping identifier used to scope the row to a specific business group.
• LEGISLATION_CODE — The legislation under which the range table is valid, enabling localization of payroll rules.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 .. ATTRIBUTE30 — Descriptive flexfield columns; with 30 attribute segments this is one of the more heavily extended payroll tables.
• RAN_INFORMATION_CATEGORY and RAN_INFORMATION1 .. RAN_INFORMATION30 — A dedicated DFF context and 30 informational segments, commonly used to store range-table-specific reference data without consuming the standard DFF slots.
• Standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATED_LOGIN, CREATED_BY, CREATED_DATE.
• OBJECT_VERSION_NUMBER — Optimistic concurrency control used by the Oracle Applications Framework (OAF) when maintaining rows.

Common Use Cases and Queries

The most common requirement is to resolve the correct range-table value for a given date and business group during payroll processing or reporting. A typical query pattern joins PAY_RANGE_TABLES_F to payroll element tables via EARNINGS_TYPE and filters by the effective date window.

Example: retrieve the current effective cells for a range table and business group.

• SELECT rt.RANGE_TABLE_NUMBER, rt.ROW_VALUE_UOM, rt.PERIOD_FREQUENCY, rt.EARNINGS_TYPE, rt.LEGISLATION_CODE FROM HR.PAY_RANGE_TABLES_F rt WHERE rt.RANGE_TABLE_ID = :p_range_table_id AND rt.BUSINESS_GROUP_ID = :p_business_group_id AND TRUNC(SYSDATE) BETWEEN rt.EFFECTIVE_START_DATE AND rt.EFFECTIVE_END_DATE;
• Date-effectivity is the primary filter for every reporting path; a payroll run date must lie between EFFECTIVE_START_DATE and EFFECTIVE_END_DATE to return the applicable cell.
• Audit and tuning queries typically select the WHO audit columns and RANGE_TABLE_NUMBER to trace who changed a specific bracket.
• DFF extraction queries pivot on ATTRIBUTE_CATEGORY and RAN_INFORMATION_CATEGORY to surface custom range-table metadata.

Practical reporting use cases include statutory tax and withholding grids, benefits coverage-rate tables, seniority- or grade-based wage schedules, and any lookup where one input selects a row and a second input selects a column. Because the table is date-effective, month-over-month comparisons of range tables are a frequent reconciliation exercise.

Related Objects

Although the mined relationship data classifies PAY_RANGE_TABLES_F as standalone, it is functionally bound to several other payroll and general-purpose objects.

• PAY_RANGE_TABLES_F_PK — the composite primary key (RANGE_TABLE_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE) and unique index; it is the join anchor for any query on this table.
• PAY_RANGE_TABLE_COLUMNS_F — typically defines the column (second) input of the range table; joined via RANGE_TABLE_ID and the shared effective-date columns.
• PAY_RANGE_TABLE_STRUCTURES (and its range-table header/definition tables) — hold the table's structural definition (rows and columns); RANGE_TABLE_ID joins them to this table.
• PAY_ELEMENT_TYPES_F — earnings element definitions; joined on EARNINGS_TYPE to resolve which element consumes the range-table cell.
• PAY_ELEMENTS and PAY_ELEMENT_ENTRY_VALUES_F — entry values that feed or reference range-table inputs during element entry.
• FND_LOOKUP_VALUES / PAY_LOOKUPS — supply the enumeration for LEGISLATION_CODE, PERIOD_FREQUENCY, and ROW_VALUE_UOM lookups.
• HR_LOOKUPS or the HR legislative data model tables — provide the business group and legislation context.

API access to range tables is generally performed through the Oracle Payroll range-table maintenance forms or via dataloader and HRMS APIs that respect date-effectivity; direct DML should be avoided because the effective-dating datetrack mechanism governs row integrity. Any integration reading PAY_RANGE_TABLES_F should always constrain BUSINESS_GROUP_ID and the effective date interval to avoid returning stale or cross-legislation rows.