Search Results ben_py_bss_rt_f




Overview
Explore in AI Chat

Overview

BEN_PY_BSS_RT_F is a table in the BEN (Advanced Benefits) product module of Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. It stores the rates that are applicable to a pay basis within Oracle Advanced Benefits. In the benefits configuration model, a pay basis defines how compensation is measured (for example, salary, hourly, or a custom basis), and the records in this table attach the qualifying rate definitions that drive benefit calculations against that basis. The object is owned by the BEN schema and is documented with 45 physical columns in the ETRM 12.2.2 schema.

The table is an effective-dated entity; it is date-tracked through EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, which participate in the primary key. This allows multiple historical versions of a pay basis rate configuration to coexist, with only the version covering a given date being logically current. A heuristic Data Vault classification based on the foreign key structure suggests treating this as a standalone or satellite-style object: it carries descriptive attributes and effective dating tied to a parent key, rather than acting as a pure hub or link. This classification is a modeling suggestion only and should be validated against the actual integration design.

Key Information Stored

The core identity of each row is the surrogate primary key PY_BSS_RT_ID, combined with the effective dating columns EFFECTIVE_START_DATE and EFFECTIVE_END_DATE. The unique index BEN_PY_BSS_RT_F_PK is defined on these three columns, making them the business-key candidate for the table.

Common Use Cases and Queries

Typical usage centers on benefits configuration validation and rate reporting. A common query verifies which rates are attached to a pay basis as of a given date:

SELECT py_bss_rt_id, pay_basis_id, vrbl_rt_prfl_id, ordr_num, exld_flag
FROM ben.ben_py_bss_rt_f
WHERE pay_basis_id = :p_pay_basis_id
AND SYSDATE BETWEEN effective_start_date AND effective_end_date;

Reporting scenarios include auditing rate precedence using ORDR_NUM, identifying excluded rates via EXCLD_FLAG, and reconciling the descriptive flexfield attributes (PBR_ATTRIBUTE1–30) against configuration standards. Because the table is date-effective, reports that back-date calculations must join on the effective range rather than assuming a single current row.

Related Objects

The documented foreign key establishes the primary relationship to the pay basis definition. Additional dependencies arise through the variable rate profile and business group references implied by the columns.

  • PER_PAY_BASES — Parent of the PAY_BASIS_ID foreign key; defines the pay basis.
  • BEN_PY_BSS_RT_F_PK — Primary key unique index on PY_BSS_RT_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE.
  • Variable rate profile tables — Referenced via VRBL_RT_PRFL_ID; supply rate values used by this configuration.
  • Business group tables (HR_ALL_ORGANIZATION_UNITS / FND_BUSINESS_GROUP) — Scope rows through BUSINESS_GROUP_ID.
  • Advanced Benefits calculation APIs — Consume these rate records when deriving benefit amounts.