Results for “egn_attribute30”

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

Overview

BEN_ELIG_GNDR_PRTE_F is a database table in the BEN schema, owned by the Oracle Advanced Benefits (BEN) application module. It stores gender-based eligibility participation prerequisites that determine whether a person is eligible for a specific benefit program, plan, or option. In Oracle EBS Release 12.1.1 and 12.2.2, this table is one of the eligibility rule lines generated and evaluated by the Advanced Benefits eligibility engine, which combines multiple criteria tables (gender, age, compensation, employment, hours, and so on) to build eligibility profiles.

The table follows the standard Oracle date-tracked (datetrack) design, which uses effective start and end dates to maintain a historical record of configuration changes. The ETRM metadata classifies the object as a standalone entity based on its foreign key profile: it has no incoming or outgoing foreign key documentation in the mined relationship data. From a Data Vault modeling perspective, this classification suggests treating BEN_ELIG_GNDR_PRTE_F as a standalone satellite-like structure. However, practitioners should note that the object references the eligibility profile through the ELIGY_PRFL_ID column even though no formal FK constraint is recorded, so a hub-and-satellite treatment of the eligibility profile and its criteria lines remains a reasonable modeling option.

Key Information Stored

The table contains 47 documented columns. The most important are:

• ELIG_GNDR_PRTE_ID — The system-generated identifier for the gender eligibility prerequisite record.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — The datetrack columns that define the validity window of each configuration row.
• ELIGY_PRFL_ID — Identifies the parent eligibility profile to which this gender criterion belongs.
• BUSINESS_GROUP_ID — The enterprise or business group context for the record, supporting multi-organization deployments.
• EXCLD_FLAG — Indicates whether the gender rule is inclusionary or exclusionary, i.e., whether matching the specified gender value grants or denies eligibility.
• SEX — The gender value being evaluated against the person's sex or gender attribute.
• ORDR_NUM — The evaluation order of the criterion line relative to other criteria in the profile.
• CRITERIA_SCORE — The score assigned to this criterion when the eligibility profile is evaluated in a scored or weighted context.
• CRITERIA_WEIGHT — The weight applied to the gender criterion in weighted eligibility calculations.
• EGN_ATTRIBUTE_CATEGORY and EGN_ATTRIBUTE1 through EGN_ATTRIBUTE30 — A descriptive flexfield (DFF) segment set, providing extensible, customer-defined attributes for capturing additional eligibility information.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — Audit columns maintained by the Oracle Applications framework.
• OBJECT_VERSION_NUMBER — The optimistic locking version used by the Oracle framework during concurrent updates.

The primary key BEN_ELIG_GNDR_PRTE_PK is a composite surrogate key comprising ELIG_GNDR_PRTE_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE. Because the same physical key columns include the datetrack dates, the PK also functions as the unique business-key candidate; the metadata documents no separate non-datetrack unique index on this table.

Common Use Cases and Queries

The most common reporting scenario is to extract all gender criteria for a given eligibility profile, typically for audit, documentation, or troubleshooting purposes. A representative query joins the criterion line to the eligibility profile and restricts to the current effective row:

• SELECT c.ELIG_GNDR_PRTE_ID, c.ELIGY_PRFL_ID, c.SEX, c.EXCLD_FLAG, c.ORDR_NUM FROM BEN_ELIG_GNDR_PRTE_F c WHERE c.ELIGY_PRFL_ID = :p_profile_id AND SYSDATE BETWEEN c.EFFECTIVE_START_DATE AND c.EFFECTIVE_END_DATE ORDER BY c.ORDR_NUM;
• Change-tracking queries compare overlapping effective date ranges to see how a profile's gender rules evolved over time.
• Migration and setup-validation scripts count criteria lines per profile to confirm that all profiles were configured consistently across business groups.
• DFF exploration queries select EGN_ATTRIBUTE_CATEGORY and the EGN_ATTRIBUTE1–30 columns to surface customer-specific eligibility details in reports.

Related Objects

The following objects are most significant in relation to BEN_ELIG_GNDR_PRTE_F:

• BEN_ELIGY_PRFL_F — The eligibility profile header referenced by ELIGY_PRFL_ID.
• BEN_ELIGY_PRFL — The eligibility profile base or view associated with the header.
• BEN_ELIG_DPNT_OTHR_F / BEN_ELIG_DPNT_CVG_F — Sibling eligibility criterion tables that follow the same datetrack pattern.
• BEN_ELIG_PER_ELCTBL_CHC_F — The plan or option eligibility linkage through which gender criteria ultimately affect enrollment.
• BEN_PTIP_ELIGY_PRFL — The association between eligibility profiles and plan-type participation or program records.

Because the table is standalone per the documented FK metadata, join relationships to these objects should be constructed on the shared ELIGY_PRFL_ID column and confirmed against the customer's configuration rather than assumed from enforced constraints.