Search Results eligy_prfl

Overview

APPS.BEN_ELIG_COMP_LVL_PRTE_D is a reporting view in the Oracle E-Business Suite Advanced Benefits (BEN) module. Its name decomposes as "Eligibility Compensation Level Profile Detail." The view presents rows from the eligibility compensation level profile participation criterion, denormalizing the numeric foreign keys held on the base table into recognizable business names for compensation level factors, eligibility profiles, excluded flags, and the user who last updated each row.

The view is read-only and is intended for inquiry, reporting, and integration purposes rather than transactional maintenance. Because it resolves foreign keys against descriptive lookups, it is useful wherever a functional or technical user must interpret compensation level eligibility criteria without performing manual joins. In Oracle EBS 12.1.1 and 12.2.2 the object is defined identically in the APPS schema. Note that the view text filters rows by an effective-date join: the base row's effective start date must fall within the effective date range of its related eligibility profile.

Underlying Base Objects

Per the documented ETRM metadata, the view references the following objects:

• BEN_ELIG_COMP_LVL_PRTE_F — the driving base table, holding the eligibility compensation level profile participation criterion rows (the _F suffix denotes the date-tracked "F" table).
• BEN_COMP_LVL_FCTR — the compensation level factor definition, providing the factor name.
• BEN_ELIGY_PRFL_F — the eligibility profile definition, providing the profile name.
• FND_USER — the application user, providing the user name of the last updater.
• HR_LOOKUPS — a view over the lookup values, used here with lookup type YES_NO to translate the EXCLD_FLAG into its meaning (Yes/No).
• HR_API — a package referenced by the object's documented dependency list.

All joins to the descriptive objects are outer joins (the (+) operator appears on the descriptive side), so a criterion row is still returned when a referenced factor, profile, or lookup cannot be resolved. The join between the base table and BEN_ELIGY_PRFL_F is constrained by effective dates rather than solely by the primary key.

Key Columns

• ROW_ID — the ROWID of the underlying base table row, used to identify a unique record.
• ELIG_COMP_LVL_PRTE_ID — the surrogate primary key of the participation criterion row.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-tracked validity range of the criterion.
• NAME — appears twice in the select list, once for the compensation level factor and once for the eligibility profile. In a query, these columns are typically aliased to distinguish them.
• MEANING — the decoded value of the excluded flag, derived from HR_LOOKUPS for lookup type YES_NO.
• ORDR_NUM — the sequence in which the criterion is evaluated or displayed.
• CRITERIA_WEIGHT and CRITERIA_SCORE — the weight and score assigned to the criterion during eligibility determination.
• LAST_UPDATE_DATE — the timestamp of the most recent change.
• USER_NAME — the FND_USER login of the person who last updated the row.

Common Use Cases and Queries

The view supports troubleshooting why a participant passed or failed an eligibility profile, auditing compensation level criteria by profile, and extracting reference data for integration or reconciliation. Because two columns are both named NAME, an explicit alias is required.

• List active criteria for a given eligibility profile:
  SELECT eligy_prfl.name profile, comp_lvl_fctr.name factor, excld.meaning excluded, ecl.ordr_num, ecl.criteria_weight FROM ben_elig_comp_lvl_prte_d ecl ... — although the view itself already exposes these; join back to BEN_ELIGY_PRFL_F only when additional profile attributes are needed.
• Identify recently changed criteria:
  SELECT elig_comp_lvl_prte_id, last_update_date, user_name FROM ben_elig_comp_lvl_prte_d WHERE last_update_date > SYSDATE - 30;
• Extract all criteria for a named profile:
  SELECT * FROM ben_elig_comp_lvl_prte_d WHERE name = '<profile name>';

All queries should be run against the APPS schema with appropriate read privileges. The view is safe for read-only reporting; it is not intended as an update target.