Results for “comp_ref”

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

Overview

BEN_ELIG_PER_D is a denormalized reporting view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It resides in the BEN (Advanced Benefits) product family and exposes the eligibility profile definition data stored in the BEN_ELIG_PER_F base table, enriched with decoded lookup meanings, plan and program names, currency descriptions, and last-updated user information. The "_D" suffix indicates that the view is intended for descriptive or display purposes rather than for transactional update; it is a read-only projection used by eligibility configuration forms, concurrent reports, and downstream integrations that need to resolve internal lookup codes and foreign keys into human-readable values without performing the joins themselves. Because eligibility rules are evaluated frequently during benefits open enrollment and life-event processing, the view provides a stable, pre-joined presentation layer that isolates callers from the physical data model.

Underlying Base Objects

The view is defined over several documented base objects. BEN_ELIG_PER_F (SYNONYM) is the primary driving table, supplying eligibility profile identifiers, effective dates, and rule parameters. BEN_LER_F (SYNONYM) provides the learning/eligibility record name exposed as LER_NAME. BEN_PER_IN_LER (SYNONYM) links persons to learning/eligibility records and is joined in the view text. FND_CURRENCIES_TL (SYNONYM) supplies currency names used for the COMP_REF_MEANING column. FND_USER (SYNONYM) resolves the LAST_UPDATED_BY identifier into a USER_NAME. HR_LOOKUPS (VIEW) is joined multiple times—once for each coded attribute such as eligibility type, age, length of service, hours worked boundary period, participation override reason, and coverage restriction—to translate lookup codes into meanings. PER_ALL_PEOPLE_F (SYNONYM) is also referenced by the view text. The documentation notes an HR_API (PACKAGE) reference in the metadata, indicating dependency on HR API logic for derived attributes. This layered join structure enables the view to present both raw and decoded values in a single result set.

Key Columns

The view exposes the primary key components ELIG_PER_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE, along with a ROWID-based ROW_ID. Core rule columns include COMP_REF_AMT (compensation reference amount) and its decoded COMP_REF_MEANING from the currency table—the value most directly associated with the user's "comp_ref" search. AGE_VAL and LOS_VAL carry the age and length-of-service thresholds, with AGE_MEANING and LOS_MEANING providing their lookup descriptions. HRS_WKD_VAL and HRS_WKD_BNDRY_PERD_MEANING describe hours-worked criteria and the boundary period. Percent full-time is held in PCT_FL_TM_VAL. Participation window controls appear as PRTN_STRT_DT, PRTN_END_DT, PRTN_OVRIDN, PRTN_OVRIDN_RSN, and PRTN_OVRIDN_THRU_DT. Waiting period dates are WAIT_PERD_STRT_DT and WAIT_PERD_CMPLTN_DT. Freeze flags (FRZ_AGE, FRZ_CMP_LVL, FRZ_HRS_WKD), distribution restriction (DSTR_RSTCN), and waived plan (PL_WVD) are also decoded. Audit columns LAST_UPDATED_BY and LAST_UPDATE_DATE close the structure.

Common Use Cases and Queries

Typical uses include auditing compensation-based eligibility rules, validating that lookup values resolve correctly, and feeding enrollment extracts. A representative query retrieves active profiles with currency context:

• SELECT elig_per_id, comp_ref_amt, comp_ref_meaning, age_val, los_val, last_updated_by, last_update_date FROM apps.ben_elig_per_d WHERE TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;
• SELECT elig_per_id, pl_key_ee_meaning, pl_highly_compd_meaning, elig_meaning FROM apps.ben_elig_per_d WHERE comp_ref_amt IS NOT NULL;
• SELECT l.lookup_code, d.comp_ref_meaning FROM apps.ben_elig_per_d d, apps.fnd_currencies_tl l WHERE d.elig_per_id = :p_id;

Because the view performs numerous outer joins, queries should filter on effective dates and eligibility identifiers to avoid full scans, and any reporting requirement for current-row-only data should apply the standard effective-dating predicate rather than relying on the view text alone.