Results for “ben_eligy_prfl_v”

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

Overview

BEN_ELIGY_PRFL_V is a view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Advanced Benefits (BEN) module. It presents eligibility profile definitions maintained by the Oracle Advanced Benefits application, exposing a single logical row per eligibility profile record together with its effective dating and the extensive set of eligibility criterion flags that determine how the profile is evaluated during benefits enrollment and eligibility processing. The view is documented in the E-Business Suite Technical Reference Manual (ETRM) for release 12.2.2 and is marked with a "Retrofitted" description, indicating that its definition was carried forward from earlier forms-based architecture into the current release while preserving backward-compatible column naming and semantics.

Because the view surfaces the full eligibility profile structure — including status, assessment method, business group, and dozens of criterion flags — it serves as the principal read-only interface for reporting and integration against eligibility profile configuration. Custom reports, extracts, and interfaces use it rather than querying the underlying table directly, insulating them from physical storage details such as the ROWID-based row identifier exposed as ROW_ID.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, BEN_ELIGY_PRFL_V is defined over the base object BEN_ELIGY_PRFL_F, accessed through a SYNONYM in the APPS schema. A second documented reference is FND_SESSIONS (SYNONYM), which is the standard Oracle Application Object Library session table and is typically referenced to resolve session context such as the effective business group or runtime environment. The view text confirms this relationship: it selects from the ELP alias of BEN_ELIGY_PRFL_F, projecting ROWID as ROW_ID alongside the profile identifier, effective dates, descriptive attributes, audit columns, server-side flag columns, and the ELP_ATTRIBUTE1 through ELP_ATTRIBUTE30 descriptive flexfield columns.

The _F suffix on the base table denotes the "foundation" or date-tracked table in the BEN datetrack convention, meaning records are effective-dated through EFFECTIVE_START_DATE and EFFECTIVE_END_DATE rather than through separate date-tracked views. The view therefore traverses the datetrack model directly, and applications must apply appropriate date predicates when querying current versus historical profile definitions.

Key Columns

• ELIGY_PRFL_ID — Primary key of the eligibility profile; the join key to dependent BEN tables such as profile-level criteria and eligibility profile relationships.
• ROW_ID — The underlying ROWID of the base table row, used as a unique row locator.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Datetrack effective dating governing when the profile definition is valid.
• NAME / DESCRIPTION — User-defined profile name and description.
• STAT_CD — Status code controlling whether the profile is active or inactive.
• ASMT_TO_USE_CD — Assessment code indicating how the profile criteria are evaluated (for example, all criteria versus any criterion).
• BUSINESS_GROUP_ID — Owning business group, aligning the profile with the HR security and legislative context.
• ELIG_*_FLAG columns — A large family of criterion flags (ELIG_AGE_FLAG, ELIG_LOS_FLAG, ELIG_JOB_FLAG, ELIG_GRD_FLAG, ELIG_PYRL_FLAG, ELIG_ORG_UNIT_FLAG, ELIG_LGL_ENTY_FLAG, ELIG_WK_LOC_FLAG, ELIG_CMBN_AGE_LOS_FLAG, and many others) that indicate which eligibility criteria are enabled for the profile.
• ELIG_ENRLD_PLIP_FLAG / ELIG_ENRLD_PTIP_FLAG — Flags governing eligibility for enrollment in plan-in-program and program-in-plan constructs.
• ELP_ATTRIBUTE_CATEGORY and ELP_ATTRIBUTE1–30 — Descriptive flexfield context and segment columns for customer-defined profile attributes.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER for concurrency and auditing.
• ELIGY_PRFL_RL_FLAG — Indicates whether eligibility profile relationships are used to combine profiles.

Common Use Cases and Queries

Typical uses include validating eligibility profile configuration, reconciling profiles across business groups, driving benefits eligibility extracts, and investigating why a participant was or was not deemed eligible. Because the base table is date-tracked, queries should constrain effective dates to return the intended version of each profile.

The following query lists active eligibility profiles for a business group as of the current date:

• SELECT eligy_prfl_id, name, description, stat_cd, asmt_to_use_cd
FROM apps.ben_eligy_prfl_v
WHERE business_group_id = :p_business_group_id
AND stat_cd = 'A'
AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;

A second common pattern retrieves profiles that have a particular criterion enabled, for example profiles using the age criterion:

• SELECT eligy_prfl_id, name, effective_start_date, effective_end_date
FROM apps.ben_eligy_prfl_v
WHERE elig_age_flag = 'Y'
AND business_group_id = :p_business_group_id
ORDER BY name;

For point-in-time auditing, substituting a bind date for SYSDATE in the effective date predicate returns the profile definition as it existed on that date, provided a row spans the requested date. Joins to the profile identifier are then used to retrieve dependent criteria, relationships, and plan or program associations from the related BEN tables, making BEN_ELIGY_PRFL_V the natural entry point for eligibility profile reporting in both 12.1.1 and 12.2.2 environments.