Results for “ben_elig_gndr_prte_v”

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

Overview

BEN_ELIG_GNDR_PRTE_V is an Oracle E-Business Suite Advanced Benefits (BEN) view owned by the APPS schema. It exposes the gender-based eligibility profile participation criteria used by Oracle Advanced Benefits to determine whether a person qualifies for, or is excluded from, a specific eligibility profile based on gender. Eligibility profiles in Advanced Benefits drive program, plan, and option eligibility; gender criteria are one of the qualifying factors that can be combined with age, service, compensation, hours worked, and other eligibility determinants to build complex eligibility rules.

The view follows the standard Oracle EBS date-tracked view pattern. Rather than exposing the underlying base table directly, it filters rows to the single effective record for the current session by restricting on the effective date range. This means downstream reports, concurrent programs, and integrations that query the view always receive the currently active gender criteria row rather than the full history. The presence of the "egn_attribute1" through "egn_attribute30" columns confirms that the underlying table carries the standard Oracle EBS DDF (descriptive flexfield) attribute set, with ATTRIBUTE_CATEGORY providing the descriptive flexfield context for those thirty columns. This is directly relevant to users who search for terms such as egn_attribute30, since the view projects that column at the top level.

Underlying Base Objects

The view is defined over two referenced base objects, both accessed through APPS synonyms:

• BEN_ELIG_GNDR_PRTE_F — the core table holding gender eligibility participation criteria records. The view aliases this as EGN and projects its columns, using EGN.ROWID as the exposed ROW_ID pseudo-column.
• FND_SESSIONS — the Oracle Applications session table, joined to supply the session effective date. The predicate SE.SESSION_ID = USERENV('SESSIONID') retrieves the effective date that drives the date-track restriction.

The join condition EFFECTIVE_DATE BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE ensures that only the single version of each gender criteria row that is valid as of the session effective date is returned. This mirrors the date-tracked structure common to Oracle EBS datetrack-enabled views and ensures consistency between the view and the session context in which the query executes.

Key Columns

• ELIG_GNDR_PRTE_ID — primary identifier for the gender participation criteria record.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date-track boundaries for the criteria row; used in the date-track predicate.
• BUSINESS_GROUP_ID — the business group to which the criteria belong.
• ELIGY_PROFILE_ID — foreign key to the eligibility profile that the gender criterion is part of.
• ORDR_NUM — sequencing order of this criterion within the profile.
• EXCLD_FLAG — indicates whether the criterion includes or excludes the matching population.
• SEX — the gender value against which the person is evaluated.
• CRITERIA_SCORE / CRITERIA_WEIGHT — scoring and weighting used where eligibility is based on scoring rather than pass/fail.
• EGN_ATTRIBUTE_CATEGORY — descriptive flexfield context for the attribute columns.
• EGN_ATTRIBUTE1 … EGN_ATTRIBUTE30 — descriptive flexfield segment columns; egn_attribute30 is the thirtieth segment.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER — standard Oracle EBS auditing columns supporting concurrency control and audit reporting.

Common Use Cases and Queries

Typical uses include auditing the gender criteria attached to eligibility profiles, reporting which profiles exclude by sex, extracting descriptive flexfield data including attribute30, and feeding downstream integrations with effective criteria.

• List active gender criteria by profile:

SELECT elig_gndr_prte_id, eligy_prfl_id, ordr_num, excl_flg, sex
FROM   apps.ben_elig_gndr_prte_v
WHERE  business_group_id = :p_bg_id
ORDER  BY eligy_prfl_id, ordr_num;

• Retrieve the descriptive flexfield context and attribute30:

SELECT elig_gndr_prte_id,
       egn_attribute_category,
       egn_attribute1,
       egn_attribute30
FROM   apps.ben_elig_gndr_prte_v
WHERE  egn_attribute_category IS NOT NULL;

• Identify exclusion rules referencing gender:

SELECT eligy_prfl_id, sex, effective_start_date, effective_end_date
FROM   apps.ben_elig_gndr_prte_v
WHERE  excl_flg = 'Y';

Because the view resolves the effective date from FND_SESSIONS, its output reflects the currently active version of each criteria row; historical reporting requires querying the underlying date-tracked table directly.