Results for “ben_elig_grd_prte_d”

28 results




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

Overview

The BEN_ELIG_GRD_PRTE_D view is a denormalized reporting object within the Oracle Advanced Benefits (BEN) module, owned by the APPS schema. It presents eligibility grade participation rules — the configuration records that determine which grades are included in or excluded from a given eligibility profile. Because benefits eligibility is defined through many interrelated setup tables, EBS exposes descriptive (or "D") views that join those tables to user-facing names, allowing implementers and reporting tools to read configuration data without navigating multiple foreign keys. This view is documented in ETRM as "Retrofitted," indicating it was brought forward into the current EBS 12.x data model, and it carries the standard Oracle proprietary copyright notice. In Oracle EBS 12.1.1 and 12.2.2, the object is present and valid in the APPS schema. The _D suffix follows the Oracle convention for descriptive views; it is intended for read-only query, reporting, and integration use rather than for direct DML against the underlying base tables.

Underlying Base Objects

According to the ETRM 12.2.2 metadata, BEN_ELIG_GRD_PRTE_D is defined over the following referenced base objects:

  • BEN_ELIG_GRD_PRTE_F (synonym) — the core eligibility grade participation rule table, supplying the primary key, effective dates, grade reference, eligibility profile reference, exclusion flag, and order number.
  • BEN_ELIGY_PRFL_F (synonym) — the eligibility profile header, providing the profile name joined to the rule.
  • PER_GRADES_VL (view) — the translated grade list of values, providing the grade name.
  • FND_USER (synonym) — resolving the LAST_UPDATED_BY user identifier.
  • HR_LOOKUPS (view) — the lookup values view, resolving the exclusion flag against lookup type YES_NO.
  • HR_API (package) — referenced by the metadata as a base object, related to the HR security and utility layer.

The view joins these objects with outer-join semantics (Oracle (+) notation) so that a grade participation rule row is returned even when a related grade, eligibility profile, or user lookup is not resolvable. This defensive join pattern is typical of EBS descriptive views and preserves the master rule record for reporting completeness.

Key Columns

  • ROW_ID — the row identifier from the underlying BEN_ELIG_GRD_PRTE_F record.
  • ELIG_GRD_PRTE_ID — the surrogate primary key of the grade participation rule.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-effectiveness range governing when the rule applies, central to Oracle's date-tracked (datetrack) design.
  • ELIGY_PRFL_NAME — the name of the eligibility profile to which the rule belongs.
  • GRADE_NAME — the descriptive name of the grade, resolved from PER_GRADES_VL.
  • ORDR_NUM — the evaluation order of the rule within the profile.
  • EXCLD_MEANING — the decoded meaning of the exclusion flag (for example, Yes/No), indicating whether the grade is expressly included or excluded.
  • LAST_UPDATE_DATE and LAST_UPDATED_BY — audit columns identifying when and by whom the rule was last modified.

Common Use Cases and Queries

This view is commonly used to audit eligibility profile configuration, to report which grades are included or excluded from a benefits offering, and to support data migration or integration extracts. A typical query returns the grade rules for a given profile as of a specified date:

  • Listing all grade participation rules for an eligibility profile by name.
  • Identifying excluded grades across all profiles for compliance review.
  • Extracting rule configuration for data conversion or interface load.

A representative query is:

SELECT eligy_prfl_name, grade_name, ordr_num, excld_meaning, effective_start_date, effective_end_date FROM apps.ben_elig_grd_prte_d WHERE eligy_prfl_name = :p_profile_name ORDER BY ordr_num;

Because the view exposes effective dates, date-effective filtering (for example, SYSDATE BETWEEN effective_start_date AND effective_end_date) should be applied to isolate the currently active configuration.