Results for “ben_eligy_prfl”

40 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BEN_ELIGY_PRFL is an APPS-owned, VALID view in Oracle E-Business Suite Advanced Benefits (BEN). It exposes eligibility profile definitions — the rule sets that determine whether a person, dependent, or organization qualifies for a benefit program, plan, or plan type. In ETRM 12.2.2 the object is documented under the title "View: BEN_ELIGY_PRFL" with the description noted as "Retrofitted," indicating that the view was re-engineered between release lines while preserving an interface compatible with existing forms, concurrent programs, and inbound integrations.

Functionally, the view presents each eligibility profile as a single row keyed by ELIGY_PRFL_ID and bounded by EFFECTIVE_START_DATE and EFFECTIVE_END_DATE. It carries descriptive attributes (NAME, DESCRIPTION, STAT_CD, ASMT_TO_USE_CD) alongside the ELIG_*_FLAG columns that declare which eligibility criteria types are active for the profile, such as job, hourly salaried, postal code, bargaining unit, age, length of service, and combined age and length of service.

Because it retains the ROWID of the underlying row as ROW_ID, the view is suitable both for reporting and for select-then-update patterns used by Oracle Forms and custom extensions.

Underlying Base Objects

The documented base objects referenced by BEN_ELIGY_PRFL are:

  • BEN_ELIGY_PRFL_F (SYNONYM) — the primary eligibility profile base table, supplying all column data and the ROWID.
  • FND_SESSIONS (SYNONYM) — the Applications session table, referenced as part of the view definition to support environment or session context used at runtime.

The view columns map essentially one-to-one to columns of BEN_ELIGY_PRFL_F, prefixed on the base table with ELP. This means BEN_ELIGY_PRFL acts as a thin, retrofitted projection over the base table rather than an aggregation or join-based transformation. Any insert, update, or delete performed through the view resolves to the corresponding single base row, provided the base table remains key-preserved through the ROWID column.

Key Columns

Common Use Cases and Queries

Typical reporting requirements include listing all active eligibility profiles for a business group, auditing which criteria types a profile uses, and refreshing downstream copies of eligibility data used by custom enrollment tools.

List all active profiles for a business group:

  • SELECT eligy_prfl_id, name, description, stat_cd, effective_start_date, effective_end_date FROM ben_eligy_prfl WHERE business_group_id = :p_bg_id AND stat_cd = 'A' AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date ORDER BY name;

Identify profiles that rely on age and length of service, including the combined-rule flag:

  • SELECT eligy_prfl_id, name, elig_age_flag, elig_los_flag, elig_cmbn_age_los_flag FROM ben_eligy_prfl WHERE elig_age_flag = 'Y' OR elig_los_flag = 'Y';

Because ROW_ID is exposed, a select-then-update pattern (often used in Forms-based extensions) is also supported, for example locking a row by ROW_ID and updating its DFF attributes. In all cases, restrict queries by BUSINESS_GROUP_ID and effective dates to avoid returning obsolete or cross-organization profile versions.