Results for “edb_attribute1”

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

Overview

BEN_ELIG_DSBLD_PRTE_F is a date-tracked (effective-dated) table in the BEN schema of Oracle E-Business Suite Advanced Benefits (Oracle HRMS). It identifies disabilities that are used for inclusion in or exclusion from a compensation object. In the eligibility engine, a "compensation object" is typically a plan, program, or other benefits offering; the rows in this table act as criteria rules that determine whether a person, based on a recorded disability code, qualifies for or is barred from that object.

The _F suffix denotes a "flex" table that carries an effective start and end date and supports descriptive flexfield (DFF) attributes through the EDB_ATTRIBUTE columns. Effective dating allows eligibility rules to change over time without losing historical configuration. The metadata classifies this object heuristically as standalone under the Data Vault modeling suggestion; no foreign-key relationships were mined, so it is not treated as a conventional hub, link, or satellite. This suggests it should be modeled as an independent reference/config entity whose natural business key combines the disability code with the eligibility profile context.

Key Information Stored

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

• ELIG_DSBLD_PRTE_ID — Surrogate identifier for the eligibility disability inclusion/exclusion rule row.
• DSBLD_CD — The disability code that the rule evaluates against.
• EXCLD_FLAG — Indicates whether the rule excludes (Y) rather than includes the disability.
• ELIGY_PRFL_ID — Identifier of the eligibility profile to which this disability criterion belongs.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Effective-dating bounds for the rule.
• BUSINESS_GROUP_ID — Owning business group, used for multi-tenant partitioning.
• ORDR_NUM — Sequence/ordering of the criterion.
• CRITERIA_SCORE / CRITERIA_WEIGHT — Scoring and weighting values used when criteria are evaluated with scoring logic.
• EDB_ATTRIBUTE_CATEGORY and EDB_ATTRIBUTE1-30 — Descriptive flexfield context and attribute segments.
• OBJECT_VERSION_NUMBER — Optimistic locking column for concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard audit columns.

The primary key is BEN_ELIG_DSBLD_PRTE_F_PK, defined on the composite of ELIG_DSBLD_PRTE_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE. That same composite is the only documented unique index and therefore the business-key candidate. The surrogate ELIG_DSBLD_PRTE_ID alone is not unique across the table because the effective dates extend the key.

Common Use Cases and Queries

Typical uses include auditing which disabilities are included or excluded for an eligibility profile, validating that rule configuration matches disability definitions, and reporting on effective-dated changes. A common pattern filters to the currently effective row for a given profile:

• SELECT elig_dsbld_prte_id, dsbld_cd, excld_flag, ordr_num FROM ben_elig_dsbld_prte_f WHERE eligy_prfl_id = :p_profile AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date ORDER BY ordr_num;
• Join DSBLD_CD to the disability lookup/validation source to display disability descriptions for exclusion rules.
• Compare criteria scores and weights across profiles to determine priority ordering in compensation object eligibility.

Because the table is effective-dated, date-effective API calls and the DateTrack framework should be used for inserts and updates rather than direct DML, ensuring correct .

Related Objects

Although the metadata records no mined foreign keys, the columns imply the following relationships:

• BEN_ELIGY_PRFL_F — Parent eligibility profile; joins on ELIGY_PRFL_ID.
• BEN_ELIG_COMP_OBJ_F — Compensation object definition associated with the profile.
• BEN_PRTT_ENRT_RSLT_F — Enrollment results influenced by eligibility evaluation.
• FND_FLEX_VALUES / FND_LOOKUP_VALUES — Source for DSBLD_CD validation.
• PER_BUSINESS_GROUPS — Join on BUSINESS_GROUP_ID for business group context.
• BEN eligibility APIs and the BEN_ELIGIBILITY_PL/SQL package evaluate these criteria during plan eligibility processing.