Search Results ben_eligy_prfl_rl_f




Overview
Explore in AI Chat

Overview

BEN.BEN_ELIGY_PRFL_RL_F is a date-tracked (effective-dated) table within the Oracle Advanced Benefits (BEN) module. It stores the eligibility rules attached to an eligibility profile, where each rule defines the criteria that determine whether a person or compensation object qualifies for a benefit offering. In Oracle EBS 12.1.1 and 12.2.2, this table acts as the rule-level detail behind the profile header, allowing multiple selection rules to be grouped into a single reusable eligibility profile.

The _F suffix conventionally denotes the "F" (non-translated, base) table of a date-effective entity, distinct from its associated "_VL" view used for display. The object holds 47 documented columns and is classified, via a heuristic derived from its foreign-key structure, as standalone. Under Data Vault modeling terminology this suggests a hub/satellite-style role rather than a dependent link; because no explicit foreign keys were documented, the classification should be treated as a modeling suggestion rather than a definitive relationship map.

Key Information Stored

The primary key is the surrogate key BEN_ELIGY_PRFL_RL_F_PK, composed of ELIGY_PRFL_RL_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE. This combination is also the sole documented unique index and therefore the business-key candidate, making the row uniquely identifiable by rule ID plus its effective date range.

Common Use Cases and Queries

Typical usage includes auditing which rules compose a given eligibility profile, reviewing rule ordering and scoring, and troubleshooting why a participant is or is not eligible. Because the table is effective-dated, reporting queries should filter against a specific date to avoid overlapping rows.

  • List active rules for a profile as of a date: SELECT eliGY_PRFL_RL_ID, FORMULA_ID, ORDR_TO_APLY_NUM FROM BEN.BEN_ELIGY_PRFL_RL_F WHERE ELIGY_PRFL_ID = :p_id AND TRUNC(:as_of) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE ORDER BY ORDR_TO_APLY_NUM;
  • Audit changes by joining CREATED_BY/LAST_UPDATED_BY to FND_USER.
  • Inspect DFF values via ERL_ATTRIBUTE_CATEGORY and the ERL_ATTRIBUTE1–30 columns for custom reporting.

Related Objects

Although documented FK metadata identifies this object as standalone, functional relationships exist through shared identifier columns. Significant related objects include:

Developers should validate joins against the concurrent-program and eligibility APIs in the BEN module, since the absence of documented foreign keys means referential integrity is largely enforced within application logic.