Search Results ben_elig_py_bss_prte




Overview
Explore in AI Chat

Overview

BEN_ELIG_PY_BSS_PRTE is an APPS-owned Oracle E-Business Suite view within the Advanced Benefits (BEN) module. Its name reflects its function: it exposes eligibility criteria defined against a Pay Basis (PY_BSS). In Oracle Advanced Benefits, eligibility profiles (ELIGY_PRFL) are made up of one or more eligibility criteria records, each of which tests a specific participant attribute. This view specifically supports the "pay basis" criterion type — the rule that determines whether a person qualifies for a program or plan based on how they are paid (for example, salaried versus hourly).

The view is designated in the ETRM metadata as "Retrofitted." This indicates it is a date-effective (datetracked) view that has been restructured to expose the current, effective-version rows from an underlying _F (base) table while applying the business group and session date logic required for multi-tenant, date-tracked Advanced Benefits configuration. It is intended for the runtime evaluation of eligibility and for reporting on eligibility profile setup, rather than for staging new configuration data.

As a reporting and integration object, BEN_ELIG_PY_BSS_PRTE presents a flattened, query-ready projection of the pay-basis eligibility criteria that administrators maintain in the eligibility profile setup windows. External systems and custom reports can read it without navigating the date-effective storage model.

Underlying Base Objects

The view is defined over two documented objects. The primary base object is BEN_ELIG_PY_BSS_PRTE_F, referenced as a synonym. This is the date-effective foundation table that stores every version of each pay-basis eligibility criterion, keyed by ELIG_PY_BSS_PRTE_ID together with effective start and end dates. The view selects all rows from this table whose effective date range brackets the current session date.

The second referenced object is FND_SESSIONS, also accessed through a synonym. FND_SESSIONS holds the effective date associated with the active user session. The view's WHERE clause joins to FND_SESSIONS on SESSION_ID = USERENV('SESSIONID') and returns only those _F rows where EFFECTIVE_START_DATE is less than or equal to, and EFFECTIVE_END_DATE is greater than or equal to, the session effective date. This is the standard Oracle "date-tracked view" pattern, ensuring each query sees the correct point-in-time configuration for the user's working date.

Key Columns

The view exposes the complete set of configuration and audit columns. The most significant are:

  • ELIG_PY_BSS_PRTE_ID — Primary identifier for the pay-basis eligibility criterion record.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — The date-effective range that governs which version is visible for the session date.
  • BUSINESS_GROUP_ID — The business group (legislative/enterprise) that owns the criterion.
  • PAY_BASIS_ID — The pay basis being evaluated; the core discriminator of this criterion type.
  • ELIGY_PRFL_ID — The eligibility profile to which this criterion is attached.
  • EXCLD_FLAG — Indicates whether the criterion is an inclusion (Y/N) or exclusion test within the profile.
  • ORDR_NUM — Order in which the criterion is evaluated relative to others in the profile.
  • EPB_ATTRIBUTE1–30 and EPB_ATTRIBUTE_CATEGORY — Descriptive flexfield columns carrying customer-defined context and segment values.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER, used for change tracking and optimistic locking.

Common Use Cases and Queries

Typical uses include listing all pay-basis criteria for an eligibility profile, auditing configuration, and feeding eligibility decisions into downstream integrations. The following query returns the effective pay-basis criteria for a specific profile:

SELECT elig_py_bss_prte_id,
       pay_basis_id,
       excld_flag,
       ordr_num,
       effective_start_date,
       effective_end_date
FROM   apps.ben_elig_py_bss_prte
WHERE  eligy_prfl_id = :p_profile_id
ORDER  BY ordr_num;

Because the view already filters by FND_SESSIONS, callers typically set their session effective date before running reports. To restrict results to a single business group:

SELECT p.elig_py_bss_prte_id, p.pay_basis_id, p.excld_flag
FROM   apps.ben_elig_py_bss_prte p
WHERE  p.business_group_id = :p_bg_id;

To join a pay basis to its descriptive text, combine the view with the pay basis (lookup / FND) definition using PAY_BASIS_ID. The view should be treated as read-only; maintenance of eligibility criteria occurs through the BEN setup APIs and forms, which write to BEN_ELIG_PY_BSS_PRTE_F and its related tables.