Search Results pay_basis_name




Overview
Explore in AI Chat

Overview

APPS.BEN_PY_BSS_RT_D is a read-only Oracle E-Business Suite view in the BEN (Benefits) application module, exposed under the APPS schema and registered in FND Design Data as BEN.BEN_PY_BSS_RT_D. It presents translated, user-facing descriptive information for the "Pay Basis Rates" configuration within Oracle Advanced Benefits, and is documented in ETRM with a status of VALID for both 12.1.1 and 12.2.2.

The view is classified as "Oracle Internal Use Only" and is not supported for direct customer access outside standard Oracle Applications programs. Its principal function is to resolve foreign-key identifiers held in the underlying Benefits tables into the descriptive values displayed on the Pay Basis Rates maintenance form. The user search term pay_basis_name maps directly to the view column PAY_BASIS_NAME, which is the descriptive designation of the pay basis attached to a variable rate profile. The view therefore serves as the reporting and integration surface through which descriptive rate-profile configuration is exposed without joining the base transaction tables directly.

Underlying Base Objects

Per the documented dependency metadata, BEN_PY_BSS_RT_D is defined over the following base objects:

  • BEN_PY_BSS_RT_F (SYNONYM) — the Benefits Pay Basis Rates base table, supplying the primary key PY_BSS_RT_ID, the effective dating columns, the variable rate profile reference, the excluded meaning, and the ordering number.
  • BEN_VRBL_RT_PRFL_F (SYNONYM) — the Variable Rate Profile table, joined to resolve VRBL_RT_PRFL_NAME.
  • PER_PAY_BASES (SYNONYM) — the Oracle Payroll pay basis definition table, used to resolve PAY_BASIS_NAME.
  • HR_LOOKUPS (VIEW) — the HR lookup view, used to resolve EXCLD_MEANING from the excluded lookup code.
  • FND_USER (SYNONYM) — resolves LAST_UPDATED_BY to the application user.
  • HR_API (PACKAGE) — invoked within the view logic, typically as part of date-track or effective-date handling or of the security/row resolution.

The view is referenced publicly as PUBLIC.BEN_PY_BSS_RT_D, confirming a public synonym for cross-schema access. It is a "View Type: Internal" object.

Key Columns

  • ROW_ID (ROWID, 10) — the physical row identifier of the underlying base record.
  • PY_BSS_RT_ID (NUMBER, 15) — the primary key of the pay basis rate record.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE (DATE) — the effective dating range for the configuration row; these drive date-tracked queries.
  • VRBL_RT_PRFL_NAME (VARCHAR2, 240) — the name of the variable rate profile to which the pay basis rate applies.
  • PAY_BASIS_NAME (VARCHAR2, 30) — the descriptive name of the payroll pay basis, resolved from PER_PAY_BASES. This is the column most frequently used in reporting and is the object of the user's search.
  • EXCLD_MEANING (VARCHAR2, 80) — the meaning of the excluded lookup value, resolved from HR_LOOKUPS.
  • ORDR_NUM (NUMBER, 15) — the display or processing sequence number for the rate record.
  • LAST_UPDATE_DATE (DATE) and LAST_UPDATED_BY (NUMBER, 15) — Standard Who columns recording the last modification date and the FND_USER.USER_ID of the modifying user.

Common Use Cases and Queries

Typical uses include Benefits configuration reporting, data migration validation, and integration extracts that must expose pay basis rate setups with their descriptive names rather than raw identifiers. Because the view is date-tracked, queries should normally constrain against a specific effective date.

Retrieve all current pay basis rate configurations with descriptive names:

  • SELECT py_bss_rt_id, effective_start_date, effective_end_date, vrbl_rt_prfl_name, pay_basis_name, excld_meaning, ordr_num FROM apps.ben_py_bss_rt_d WHERE SYSDATE BETWEEN effective_start_date AND effective_end_date ORDER BY vrbl_rt_prfl_name, ordr_num;
  • SELECT vrbl_rt_prfl_name, pay_basis_name, ordr_num FROM apps.ben_py_bss_rt_d WHERE pay_basis_name = :p_pay_basis_name AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;

For audit purposes, join LAST_UPDATED_BY to FND_USER to display the modifier's user name, and always apply an effective-date predicate to avoid returning historical or future-dated configuration rows.